On Jan 3, 2006, at 4:01 PM, Matthew Schmidt wrote:
Definitely useful, but I question how we plan on blocking requests
from
referrers that are bad? If everything is pushed into the queue,
wouldn't
the request just continue as normal with the blacklist processing
happening
later?
Yes, that appears to be a shortcoming of this proposal.
If we want to answer referrer spammers with a 403 access denied, as
we do now, then I guess we could do something like this: when the
request comes in, check it against the blacklist, which is in memory.
If it matches, then pitch it out with a 403. Otherwise, put it in the
queue for storage in the DB.
With that approach, we'd still do some work for each referrer but we
wouldn't have to hit the DB.
- Dave
-Matt
-----Original Message-----
From: Allen Gilliland [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 03, 2006 3:18 PM
To: [email protected]
Subject: Proposal: Asynchronous Referrer Processing
This is already linked on the Roller 2.2 proposal page, but I thought
I'd send it out directly as well.
http://rollerweblogger.org/wiki/Wiki.jsp?
page=AsynchronousReferrerProcessing
This will allow Roller admins to optionally process referrers in an
asynchronous manner, i.e. not tied to the http request/response cycle.
Thoughts/comments always welcome.
-- Allen
