Re: [ogpx] Transport independence (Re: Next Steps for OGPX WG Charter)

[Mojito Sorbet <[e-mail]>]

Meadhbh missinterpreted my points.  I did not say that XMPP  is 
transferring multiple documents,  but exactly ONE document, according to 
what the syntax rules of XML are.    There is an opening tag when the 
session opens, and the closing tag is not sent until the session 
closes.  At a syntax level, they are transferring xml stanzas, very 
slowly.  In fact those represent events, but they have the the form of xml.

Similarly we could send an HTTP header, followed by a series of 
<something> (and certainly not base64 coded), and claim to be using an 
HTTP transport.

Also, I specifically said that large objects like textures WERE an 
obvious candidate to send as independent HTTP transfers.  I would do 
that over a separate channel, so as not to tie up the shorter events.


------------------------------------------------------------------------

On Tue, Aug 4, 2009 at 7:03 PM, Mojito Sorbet<mojitotech at gmail.com> wrote:
>> Similarly XMPP sends an XML 'document'
>> that takes HOURS to send, very slowly, one stanza at a time;  in fact both
>> ways at once.

Meadhbh Siobhan wrote:
>i think the XMPP people would argue that it's sending event stream
>updates using XML stanzas, not complete documents.