There are a couple of ways to play this: 1) put (copies of) your servlets in a different protection domain, and authenticate the client by ipaddress and/or digital certificate. This only works if you dont need the session, ie all the state is held in the fat client. 2) Teach the client to do cookies. (which isnt too hard, httpunit.sourceforge.net does it.)
As for SOAP, I'd also like to know what people think. URL: http//www.westpoint.ltd.uk/ - internet recon. ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
