<br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I think these requirements strictly doesn't claim that a stateful web<br>service should be written. You could also gather these information at
<br>the client side and specify those as URL parameters or postdata for<br>the server application.</blockquote><div><br> Application has to be stateful becouse "protocol" is documented and this is requirement of my bussiness client.
<br>Currently my company's client has simmilar webservice(based on MapXtreme) which should be change to something faster, more stable and of course cheaper:) but with the same interface. A few applications is connected to webservice. Changing interface to stateless would affect all those applications. So it is not under consideration.
<br></div><br></div><br>Best Regards,<br>Adrian Kruk<br clear="all"><br>