[EMAIL PROTECTED] wrote:
>
> Well, that obviously wasn't happening at a recent trade show - on
> location, our
> application was behaving strangely (taking 15-20 times longer to
> execute, sharing
> session data...). So, SOMETHING was going on - since we aren't doing
> URL rewriting
> ourselves, the client-side cookies were getting set to the same cookie!
> We attribute
> that to going through a proxy server on site. Maybe the proxy server
> wasn't set up
> properly or something, I don't know.
My experience is actually with Resin. I've run multiple clients on a
single machine, each with its own session, no problem. I've done it
both with cookies and with URL rewriting. (We switched to URL rewriting
because of FUD about cookies being evil.)
Is TomCat's (or whatever you're using) session identification stuff broken?
If so, it's not that hard to add your own session IDs. Gee, that would
stink, though.
--
Richard Kasperowski (mailto:[EMAIL PROTECTED])
Tel: 617-576-1552, Fax: 617-576-2441
http://www.altisimo.com/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
