ok, all clear! One point though: with a threaded webserver web2py can manage as many connections as there are free threads: it's not blocking everything at the first SSE yielding loop, it doesn't communicate with new connections as soon as there are n open connections, with n == max number of threads. I can't test it right now, but rocket (that is the "embedded" webserver of web2py) unless specified explicitely, opens a new thread at every connection (if you don't set the maxthreads option). Of course this can't scale up to 1000 connections, but its nonetheless sufficient for testing purposes or a small userbase.
-- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
