Difference between revisions of "Talk:Reverse HTTP"
Jump to navigation
Jump to search
m (→More reading: new section) |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 2: | Line 2: | ||
* Strife, every problem containing symmetrical higher-level relationships between two parties could fit this solution. | * Strife, every problem containing symmetrical higher-level relationships between two parties could fit this solution. | ||
* As one example of direct relevance to our current MMOX work at the IETF, consider two interoperating virtual world providers, who as peers are perfectly symmetrical in their relationship to each other at the VW level, but one of | * As one example of direct relevance to our current MMOX work at the IETF, consider two interoperating virtual world providers, who as peers are perfectly symmetrical in their relationship to each other at the VW level, but one of whom is isolated from incoming external access within a corporate protection domain. Reverse HTTP would allow totally symmetric application-level operation, despite the assymetry at the TCP level. | ||
* The high-volume example is of course the desire for elegant communication between SL servers and SL viewers, given that the hosts upon which viewers are run only rarely are reachable and support incoming TCP connections. [[User:Morgaine Dinova|Morgaine Dinova]] 14:12, 8 March 2009 (UTC) | * The high-volume example is of course the desire for elegant communication between SL servers and SL viewers, given that the hosts upon which viewers are run only rarely are reachable and able to support incoming TCP connections. [[User:Morgaine Dinova|Morgaine Dinova]] 14:12, 8 March 2009 (UTC) | ||
== empty response body == | == empty response body == | ||
| Line 10: | Line 10: | ||
Is there a reason 204 No Content isn't being used ? | Is there a reason 204 No Content isn't being used ? | ||
- [[User:SignpostMarv Martin|SignpostMarv Martin]] 08:16, 14 July 2008 (PDT) | - [[User:SignpostMarv Martin|SignpostMarv Martin]] 08:16, 14 July 2008 (PDT) | ||
== More reading == | |||
I think this idea has been abandoned - however some more details may be found in [http://donovanpreston.blogspot.com/2008/12/ptth-reverse-http-implementation-in.html ptth (Reverse HTTP) implementation in a browser using Long Poll COMET] by Donovan Preston. --[[User:Opensource Obscure|oobscure]] 19:12, 12 January 2010 (UTC) | |||
Latest revision as of 11:12, 12 January 2010
What applications are there for this? I'm having trouble envisioning a problem that fits this solution. -- Strife Onizuka 13:26, 14 May 2008 (PDT)
- Strife, every problem containing symmetrical higher-level relationships between two parties could fit this solution.
- As one example of direct relevance to our current MMOX work at the IETF, consider two interoperating virtual world providers, who as peers are perfectly symmetrical in their relationship to each other at the VW level, but one of whom is isolated from incoming external access within a corporate protection domain. Reverse HTTP would allow totally symmetric application-level operation, despite the assymetry at the TCP level.
- The high-volume example is of course the desire for elegant communication between SL servers and SL viewers, given that the hosts upon which viewers are run only rarely are reachable and able to support incoming TCP connections. Morgaine Dinova 14:12, 8 March 2009 (UTC)
empty response body
Is there a reason 204 No Content isn't being used ? - SignpostMarv Martin 08:16, 14 July 2008 (PDT)
More reading
I think this idea has been abandoned - however some more details may be found in ptth (Reverse HTTP) implementation in a browser using Long Poll COMET by Donovan Preston. --oobscure 19:12, 12 January 2010 (UTC)