Sure, that would certainly be a good way to make the information available across clustered DBMails so that we have the information handy in order to prevent one user / ip from storming the cluster.
I want to slowly build out the information we have available now, along the stable series, so that we learn more about what needs to be there in the future. Aaron On Fri, Apr 6, 2007, Jesse Norell <[EMAIL PROTECTED]> said: > What about memcache for this type of stuff? I know it mean it'll be in > 2.3, not 2.2, but that may be an appropriate cost/benefit decision. > > > > On Fri, 2007-04-06 at 09:34 -0700, Aaron Stone wrote: >> >> > - total number of concurrent connections opened (so we can limit the >> number of >> > connections a single client has opened, maybe) >> > - cumulative number of connections per remote ip >> >> Interesting, what if we did this in a second area of the shared >> memory, >> with a new structure that held info on a per-remote-ip basis. We could >> have a fixed window and purge it according to the LRU entries, so that >> we'd always have a list of the 50 or 100 most frequent visitors' ip's. >> > -- > Jesse Norell - [EMAIL PROTECTED] > Kentec Communications, Inc. > > _______________________________________________ > Dbmail-dev mailing list > [email protected] > http://twister.fastxs.net/mailman/listinfo/dbmail-dev > -- _______________________________________________ Dbmail-dev mailing list [email protected] http://twister.fastxs.net/mailman/listinfo/dbmail-dev
