Yes, that should work well.
thanks
On Oct 21, 3:24 am, Dave 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, the
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
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 applicati
