[Seaside] Goods connection limit
William E Harford
seaside at harford.org
Wed Sep 7 21:51:53 CEST 2005
I created a subclass of WASession to handle a connection to GOODS. It
allows my easy and almost transparent access to persistent storage. This
seams to be a very common way to handle GOODS with Seaside.
I have come across a problem in which I am not to sure there is a
perfect solution to. For some reason goods will only allow about 200
connections. After that my Seaside apps (the ones whose sessions have
not connected to the database) will lockup and wait for goods to allow
new connections; after some stale sessions have been unregistered.
We plan on servicing much more than 200 concurrent users so this is a
bit of a problem. Also to DOS a Seaside application that relies on GOODS
is trivial. A simple `while true; do wget "http://bla.ca/seaside/bla";
done` will do it.
I tried initiating a GOODS connection at the start of a continuation and
ending it at the end of a continuation but this caused major problems
and crashed the image (understandable). Even if I could make this work
or is even possible I don't think this would be such a good solution
because I would loose the local cache (right?).
I am starting to think I have 2 distinct problems and it will require 2
1) Allowing > 1000 concurrent database connections.
I can't seam to find a way to tell goods to allow more than ~200
connections. I don't see any reason why GOODS can not allow thousands or
even tens of thousands (given enough fire power) of connections.
2) Limit the ability for someone to DOS our applications. This could be
something as simple as limiting the number of connections from an IP
Any ideas on how I could best handle this ?
William E Harford <seaside at harford.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Seaside