Re: pipelining setting

Lee <[email protected]> wrote:

> On 6/28/13, Robert Max Jackson <[email protected]> wrote:
> >     For Privoxy version 3.0.21, after rereading sections 6.5 of
> > config.txt on tolerate-pipelining repeatedly, I cannot figure out
> > which setting, 0 or 1, tolerates pipelining.  (I fear the
> > documentation here is completely ambiguous, at least for those not
> > familiar with whatever linguistic assumptions would make it
> > unambiguous.)
> >
> >     Could someone clarify?
> 
> 0: privoxy does not handle pipelined requests
> 1: privoxy attempts to handle pipelined requests from the client (eg. firefox)
> 
> #  Effect if unset:
> #
> #      If Privoxy receives more than one request at once, it
> #      terminates the client connection after serving the first one.
> 
> I'm so used to 1 is the same thing as "set" and 0 is "clear" or
> "unset" that it's hard for me to imagine someone not knowing that --
> assuming that is the problem with the documentation.
> 
> How would you change the documentation to make it clear that
> 0 = client pipelining is not allowed
> 1 = client pipelining allowed

I suppose we could change "This option lets Privoxy tolerate pipelining."
to something like "Setting this directive to 1 lets ...".

> Fabian - is this bit correct?
> 
> #  Default value:
> #
> #      None
> 
> sure looks like the default is 0

In the config file "None", "Unset" and "0" currently refer to the same
numeric default value. I wouldn't be opposed to consistently using "0".

Fabian

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev

_______________________________________________
Ijbswa-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ijbswa-developers

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (FreeBSD)

iQIcBAEBCAAGBQJRzxcdAAoJEGkYIpGLojccmgMP/1dNWBsXvFwWVmg3PP4p/Hss
LrrilFpsIdPD201J17E2Q0xmdtU+srecwjH5+gblOPA3BAzE8JJ2TV6biffWUl9W
Pv/xWaie5WLL5Nn5jh+5682OtbpF5uIxdJ/aV9oVNsjwnhQrRTT/1SRDXQwji8+3
itZ+ONXdAUNihqhF33eeaMvdXB4s6eVxmBYkJ/JFU5V+mu00VuCjV4iK+ij+Hrdc
aYUPT1lDWKcvrXHV2Gbc2SNe5TCtQkZzAhS80Ap25AXsPX93B/x3xekFU5bgcHvi
yMFiilOHgQtGVJ9+HsYtk9VljKu/c4KMzQ41jSEZyitD81PB1QH1nNYWUQZjKy36
j9zeT46bFcOxZg2QwbIRf6atFI6Rew+39Z62QPFHY1EaeKjgN5gg4wkdNrIjEJUe
OZp1hMsLp73HkGZTJcq3pzDCIIFMUkIiMKvsznI1FaKrM6b0MD3XLWuhf8jfmnaG
0t1FvsAgos23V5oK3gV9PFptgGOU0L4gZYNbrD+Hqo02JNE1gTxGkIsutQClNxWu
GQ9JASht9Q6xIorz1xSdrixWQRGw7apw+G/xkqzmu4wTbOXUeRE+UlyLn+RGyjXS
2//MGHU5i1PkDrz/vtOZ1tfpuz1QG5XCn+RX2iF+XhNFwuBCfPcBXiy6eeCdk/GO
cO+Fp6GZ6kNh1JiXtz+W
=ttwH
-----END PGP SIGNATURE-----