Yes, that should work well. thanks
On Oct 21, 3:24 am, Dave <davidcr...@gmail.com> wrote: > This may not be the best solution, but I've seen this implemented > before with an IP's table. You could probably modify the afterSave in > the app_controller to insert an entry with ip address, action, and a > timestamp, then modify the beforeSave to query this table based on > your criteria (X entries in the past hour, day, etc.) > > On Oct 21, 12:21 am, calzone <calz...@gmail.com> wrote: > > > > > Has anyone worked on an app-level component that can help prevent a > > flood of submissions on a server? > > > Ideally, such a system would prevent the same person from submitting > > more than x actions where there is database writing per minute --not > > just for a single action, but across the entire application -- as well > > as imposing hourly and daily limits (per cookie, per session, per ip > > address, per ip network/subnet). I assume there would also be some > > form of blacklisting should any of those sources exceed the flood > > threshold too often. > > > For some reason, I assumed this was already built-in to cake, but > > never until today did I stop to really think about it or look into it. > > Surely many other cakebakers have thought about and dealt with this > > before? I wasn't sure what search term to use on the group to find > > out (flood control only turns up one query from a while back and it > > was specific to one single form for email). > > > What say ye? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
