in reply to Http connection manipulations
I'm not sure I understand your structure. The phrase "parent-proxies" isn't clear to me. I don't understand what socket connections exist. Client to proxy to "parent-proxy"? In that case I'd call them "servers"; they're not in any sense proxies.
Your question looks either trivial or obviously impossible, depending on what the actual structure is. Either the code with the content to return has the open socket from the client, or it doesn't. If it does, just write it there. If it doesn't, no hope. (Possibly by restructuring things completely, it could be made possible.) But my lack of understanding of the structure probably means it's not like this.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Http connection manipulations
by kazak (Beadle) on Jan 11, 2012 at 08:33 UTC | |
by flexvault (Monsignor) on Jan 11, 2012 at 14:12 UTC | |
by kazak (Beadle) on Jan 11, 2012 at 21:53 UTC | |
by flexvault (Monsignor) on Jan 11, 2012 at 22:16 UTC | |
by kazak (Beadle) on Jan 12, 2012 at 09:00 UTC | |
|