MapServer Application Design Questions

[Tamas Szekeres]

2008/1/23, adrian kruk <adrian.kruk at gmail.com>:
> Here is some description of simple example of talking protocol between
> client and server - to easier understand. It is not all functionality.
> Forget about updates, I don't need this now,  maybe in future. Application
> will be created in stateful mode.
>
>
> Many clients are connecting to webservice(my IIS application).
> Each clients has its own map session so it means that has mapobject on
> server side in session cache, on which he can set parameters like zoom,
> center point, bounding rectangle, layers visibility,etc via webservice
> methods.
> Webservice recognises proper mapobject becouse clients sends sessionId in
> each method.
> e.g. SetZoom(long sessionId, float zoom).
>
> After setting this parameters on his own map object(which is in webservice
> memory),  client requests for image by executing GetImage webservice method.
> After that image will be sended to the webservice client via SOAP from
> webservice app.
> After a while client want to see all towns with first letter "W" in name and
> marked as different color. So client executes proper method on webservice.
> WebService is creating new layer (filtered from towns) and put this layer to
> proper mapobject. After that client execute GetImage method to see those
> "w*" towns in all country (with also other layers which visibility he had
> set before).
>

Adrian,

I think these requirements strictly doesn't claim that a stateful web
service should be written. You could also gather these information at
the client side and specify those as URL parameters or postdata for
the server application.

Best regards,

Tamas