After fighting with memory-leaks in the demo-applications, as well as a concurrency bug in java.awt.EventQueue, cacio-web should be ... almost ... rock solid finally.
Guess AWT simply was never tested with 20+ concurrent sessions ;)
Even if tried already, in case you have some time left, please play arround a bit:
http://icedrobot.de:9091/SessionInitializer?cls=SwingSet2
Would be great to see it behaves also well under real-world load :)
Guess AWT simply was never tested with 20+ concurrent sessions ;)
Even if tried already, in case you have some time left, please play arround a bit:
http://icedrobot.de:9091/SessionInitializer?cls=SwingSet2
Would be great to see it behaves also well under real-world load :)
