I'm also considering the approach where I handle the sessions myself as parameters to the operations.
I've been told that it would be more scalable and somewhat faster to let the soap toolkits handle sessions in soap headers. So far, I've been sceptical to this approach for the same reasons as you mention Jarmo.
It would be great to hear what experienced Web Service developers say about this and what the most common approach is today.
/ Clarence
-----Original
Message-----
From: Jarmo Doc [mailto:[EMAIL PROTECTED]]
Sent: den 20 september 2005 00:26
To: [email protected]
Subject: Session handling, do it yourself?
I've been investigating session handling and have almost
convinced myself that for my particular situation I should just do it
myself. Each of my WS clients juggle multiple end-user sessions so the simple,
default cookie solution doesn't work on its own (because the cookie
identifies the WS
client session, not an end-user session).
I've looked into using SOAP headers but it just seems to
be too complex -- I'd have to write server code, my clients would have to
write code, plus we'd need special WSDD at both server (not too bad) and
*all* clients (very undesirable).
Also, as far as I can tell, I couldn't use java2wsdl to generate the WSDL for session handling so it would have
to be maintained manually.
So all of this is leading me to the conclusion that I
should just do it myself: have my login() operation return a string
containing a session ID and then specify that as the 1st parameter on all
subsequent session-based operations. It's
trivial code to write and the auto-generated WSDL is correct (and describes session handling to clients in a
quite obvious fashion).
Am I way off base here and missing something? Thanks.
_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
