[prev in list] [next in list] [prev in thread] [next in thread]
List: privoxy-developers
Subject: Re: [privoxy-devel] New Tags Feature
From: Fabian Keil <freebsd-listen () fabiankeil ! de>
Date: 2007-04-17 18:53:09
Message-ID: 20070417205309.38ef1ced () localhost
[Download RAW message or body]
[Attachment #2 (multipart/signed)]
Fabian Keil <freebsd-listen@fabiankeil.de> wrote:
> Currently tagging works like this:
>
> 1 Privoxy receives the request from the client
> 2 The action settings are initialised based on the URL patterns
> 3 The client-header taggers are executed
> 4 The action settings are updated base on the tags
> 5 The client-header filters are executed.
> 6 Privoxy checks if the request has to be crunched
> 7 The request is forwarded to the server
> 8 The server-header taggers are executed
> 9 The action settings are updated again
> 10 The server-header filters are executed
> 11 The content filters are executed
That's no longer true, the action bits are now also
updated directly after a new tag is set. As a result,
this limitation is gone:
> One also can't enable taggers based on tags created by
> the same type, because the client-header taggers work with
> the action settings based on step 2 only, and the
> server-header taggers with the ones from step 2 and 4.
> Changing this wouldn't be a big deal, but so far I didn't
> see the need.
The main reason was that updating the action bits
directly allows Privoxy to give feedback whether
or not a tag activated one or more tag-pattern sections.
Fabian
["signature.asc" (application/pgp-signature)]
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Ijbswa-developers mailing list
Ijbswa-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ijbswa-developers
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic