[Seaside] Concurrency question
philippe.marschall at gmail.com
Mon Feb 18 05:49:13 UTC 2008
2008/2/18, Jeffrey Straszheim <jstraszheim at comcast.net>:
> James Foster wrote:
> > In GemStone each VM is also single-threaded but you can have multiple
> > VMs attached to the same object space. Here the typical approach is to
> > use Apache to round-robin requests to separate VMs so that blocking is
> > less of an issue. See http://seaside.gemstone.com and
> > http://gemstonesoup.wordpress.com for more info.
> That sounds a little more complex than I want to deal with for my first
> Seaside app (baby steps for me). What I want to ensure is that while a
> long running thread is handling one HTTP request, other arriving HTTP
> requests will still be honored -- they are not in Rails, for instance,
> which *requires* you to run multiple instances to have any hope of low
> lag for clients (and even then, if all of your instances are busy,
> everyone else waits).
> I fully understand the difference between green threads and os level
> threads, and blocking vs. non-blocking I/O. I just want to know what
> Seaside actually does.
Seaside does the same thing the underlying platform does. It really
depends what is causing your http request to be long running.
More information about the seaside