>> It's a very rare bug, and fixing it would require keeping quite a bit
>> of additional housekeeping information; for once, I'll just give up.
> Ok. Thanks for looking into this. We'll work around it by not
> breaking the first connection until the second is complete. The
> overhead should be minimal.
Still, it does bother me quite a bit. I certainly don't want to put
a lot of effort into this issue, but I'm wondering if there's a simple
solution.
Every server-side request is owned by a client-side request; when the
owner is shut down, so is the ownee.
When a single server-side request is used to satisfy multiple
client-side ones, only one is the owner, which is what causes the
problem. Normally Polipo will automatically refetch, but if the
fetched object is uncachable, there's no way to reconcile the two
requests.
I guess something could be done to let the surviving client-side
request inherit the server-side request. The question being -- how do
you make the bookkeeping manageable?
Juliusz
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Polipo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/polipo-users
