Seen practical names filterchain just passing on more like AI then ruled based selfupdating probabilities admintting new chances blacklisted where material improved easy informatic argument: levenstein comparing content so doublets even looking good still blacklist since same same repeating alternatively Markovian no memory and states only updating probabilities according to material
On Jun 10, 1:31 am, Jaroslav Záruba <[email protected]> wrote: > Is there any reason why use memcache instead of static collection <ip, > timestamp> in a filter? It does not seem to be that important to me to share > such collection among all app. instances. Or am I wrong? > > On Thu, Jun 10, 2010 at 12:06 AM, nickmilon <[email protected]> wrote: > > There were a couple of sugested solutions using memcache for this some > > time ago in this thread. > > The problem with those solutions is that if you delegate the task to > > the request handler then you yave already started consuming cpu > > resources. > > > On Jun 9, 10:13 pm, Timothy Makobu <[email protected]> > > wrote: > > > thanks nickmilon, > > > > I had read that, that would be after the DOS though. I meant something > > that > > > detects a certain number of requests per second and does a specified > > action. > > > > like: > > > if requests_per_second > 7: > > > block_ip(ip) > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<google-appengine%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
