Geoffrey Talvola said: > If your IP sprayer supports "session affinity", where it can be configured > to examine the cookies and direct all requests for a particular session to > the same server, then Webware can be used as-is. If you make heavy use > of > session variables then this is bound to be more efficient than having to > rely on a centralized session store. > I agree that our IP sprayer probably *could* do this and that it *would* be more efficient. However, my company is so large that our development group has no direct control over the IP sprayer configuration. Getting changes made involves several other groups and a lot of paperwork. Given that the J2EE environment that they already have is implemented without the need for session affinity, I suspect that it would take the proverbial "act of God" to get them to learn how to set it up just for our application, especially since we are *supposed* to be working on porting our application to the J2EE environment.
> But, I agree, it would be nice if Webware supported a centralized session > store out of the box. > Perhaps if is would have, we would have been able to get the app ported to Webware before corporate decided that it must be re-written in J2EE. Oh well... -- Warren Smith [EMAIL PROTECTED] ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
