On Jun 16, 2010, at 09:44 PM, Stephen J. Turnbull wrote: >But IMO the pipeline architecture already does that. I haven't looked >closely at the Mailman 3 webserver, but my understanding is that it >gets a pipeline too. It seems to me that once you have that (and IMHO >that is extremely desirable just by analogy to the list processing >pipeline, which I have written several Handlers for), the rest is >going to be pretty CAPTCHA-specific, and quite possibly specific to >the particular CAPTCHA implementation.
It's an interesting idea, but I'm not quite sure how a webserver pipeline would work. The way the list server pipeline works now is by treating messages as jobs that flow through the system. A web request is kind of a different beast. -Barry
signature.asc
Description: PGP signature
_______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
