>> The solution is to use a reliable protocol, not HTTP, for RPC.
>
> I'm trying to make a bad system (which already uses HTTP for RPC)
> better here. I have complete control over the HTTP server and know
> what its behaviour is likely to be, moreover I know that resubmitting
> the POST request would not be very bad anyway in this particular case.
> Can you see anything that may go wrong.
You obviously know what you're doing, so there should be no trouble.
It wouldn't be suitable behaviour for the default configuration of
Polipo, of course.
> I intend to try to hack it anyway.
In httpServerSideRequest, replace the loop that finds a fresh
connection as well as the code that schedules connection creation in
case of failure with just something like (untested!):
connection = httpServerGetConnection(server, &numidle);
if(!connection) return 1;
Juliusz
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Polipo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/polipo-users
