Crunchy registers an output thread for each page. However, there is no way
for these threads to end. It could be that, for long running Crunchy
sessions (in a classroom server environment) that this could cause a
degradation of performance.
One way around this would be to have at most X pages open per user, keeping
track of the latest page with interaction, and killing the threads
considered to be inactive ...
Original issue reported on code.google.com by andre.ro...@gmail.com on 30 Sep 2008 at 9:53
Original issue reported on code.google.com by
andre.ro...@gmail.com
on 30 Sep 2008 at 9:53