Stateful SOAP RPC-service with HTTPS. Why?

[Hartmut Bernecker <h....@dhw.de>]

Hi @all,

Apache Soap 2.2 allows it, to make Services be stateful (with HTTP).

The documentation says:
"What that means is that if a service you are talking to via HTTP sets
the appropriate HTTP cookies to maintain the session, those will be
copied and stored in the call object used to invoke the service. If
another call is made using the same call object, then that cookie will
be sent back to the server, thus maintaining the session. Thus, all you
have to do is ensure that a single instance of a call object is used
across all the calls that you wish to make over the same HTTP session."

My Questions:

1. What is the benefit of using a single instance of a call object and a
HTTP-Session when doing RPCs via SOAP?

2. Who knows if that can be done when using Apache SOAP 2.2 (Client) and
4S4C (Server)?

_________________________________________
Hartmut Bernecker
Druckhaus Waiblingen
Siemenstrasse 10
D-71332 Waiblingen, Germany

Tel.:   +49 (0)71 51 / 5 66 - 4 48
Fax:    +49 (0)71 51 / 5 66 - 3 23
Mail:   mailto:h.bernecker@dhw.de
Web:    http://www.dhw.de/

---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org