I have now added client InetAddress stickyness, which is probably going to be good enough for 90% of cases.
But for those that want session stickyness, I have now allow delayed server allocation and pass the queued data into the Policy. This will allow a search for jsessionId up until the queue is full (at which time you had better allocated or you will just block). Only thing lacking is a monitor of the response channel so you can pick up session cookie sets. I'm now going to stop on the balancing policy and concentrate on the network stuff. Still no decent exception handling. There is also a funny in the nio (at least on Linux), where I close the Channel, the socket, the inputstream, the outputstream, etc. and the client still does not see the closed connection until it tries to write another packet! Note good for HTTP/1.0! This only happens sometimes - and never in a test harness!?!?!?!?! cheers -- Greg Wilkins<[EMAIL PROTECTED]> GB Phone: +44-(0)7092063462 Mort Bay Consulting Australia and UK. Mbl Phone: +61-(0)4 17786631 http://www.mortbay.com AU Phone: +61-(0)2 98107029 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
