On Thu, Aug 9, 2012 at 8:05 AM, Jack Moffitt <[email protected]> wrote: >> Right - but that is mainly discussing an out-of-band HTTP request with >> a custom non-standard payload. Standardizing such a payload wouldn't >> be 'informational' but clearly a protocol. On the other hand if it >> doesn't specify *how* to do it then it seems little more than a note >> to say "You can do this!" - which seems like if necessary it could >> live in the BOSH XEP itself just as easily. > > I would like to specify the how as a protocol we can all agree on. The > fact that there are 4-5 implementations all slightly different is a > bit annoying. This could easily be done by the BOSH servers themselves > with just a little bit of added protocol. > > Also, we should add initial data examples to the spec since that > appears to be a big win and is far less complicated than pre-binding. > > jack. > > PS. What are Carbons + MAM?
XEP-0280: Message Carbons XEP-0313: Message Archive Management Carbons allows replicating outgoing+incoming messages to all carbons-enabled resources of a user. MAM allows retrieving conversation history. These two combined with some extra bits allow conversations that survive on multiple tabs, through reloads and navigations, and even across websites. In the mentioned private client we fully inline these in the first BOSH request, and the client gets everything it needs on the first response. Cross-tab sessions by the way are the largest missing piece of the BOSH puzzle. It's a wide gaping hole, and we keep getting requests regarding "facebook-like chat". As far as I know, the XMPP community has no spec, no public code, not even any tutorials, blog posts or useful discussions on the topic. I would really like to see this solved. I'm certain BOSH would become a lot more attractive to the wider web developer community if we do. -- Waqas Hussain
