Hi Steve,
(B
(B> -----Original Message-----
(B> From: Steve Loughran [mailto:[EMAIL PROTECTED]]
(B> Sent: Thursday, January 16, 2003 8:12 AM
(B> To: [EMAIL PROTECTED]
(B> Subject: Re: Stateful Web Services
(B :
(B> The weakness of cookies is they are transport specific and very dependent
(B> upon implementations of HTTP, some particular weak implementations
(B> (java.net.HttpUrlConnection) handle cookies badly (it used to let you set
(B>1
(B> cookie, but them someone fixed it in 1.3 to stop you doing that).
(B>
(B> but I like them as they are simple, integrate well with the server, and
(B> integrate with load balancing level seven routers, things like ArrowPoints
(B> that make sure that requests to a cluster go back to the previous server,
(B> provided it is still happy.
(B
(B This is one of the reason why I think it's useful using the cookie based
(Bsession management on the HTTP protocol bindings, currently.
(B
(B> I dont see any soap header aware routers around, and given the lack of a
(B> standard header that isnt surprising, ignoring the details of how hard it
(B> would be to buffer and route inbound messages without actually parsing
(Bbits
(B> of them.
(B
(B Here is the additional info:
(B<http://www.f5.com/f5/news/press/release102102A.html>
(B
(BRegards,
(B
(B Toshiyuki Kimura <[EMAIL PROTECTED]>
(B R&D Headquarters
(B NTT DATA Corp.