[API] Distribution method (was Re: Jabber "API")

Tue Mar 4 16:45:50 CST 2008

Sorry for lagging, guys.  I got home ~24 hours ago and I'm still catching up.

>  Personaly, I have three action items on my side:
>
>   * finish reading through Sameplace site and docs: given that it
>  already does a lot of stuff we want to do, I want to have it in my
>  mind while we discuss this;

You'll be better off asking, I'm afraid, unless by the above you mean
"reading through the code".

A 10000ft-level view for a non-muc scenario, from the user's point of
view, would be:

- user sends contact a request to open their communication channel to
a common-ground web page;
- contact accepts;
- web page receives a roster iq containing contact's item only, as if
it had been sent by server;
- web page receives contact's presence as if it had been sent by server;
- from now on, web page sees all stanzas coming from and going to the contact;
- web page can send stanzas to the bare jid of the contact with
<message><body>...</body></message> or to a specific resource with
<message to="/Res"><body>...</body></message>

The outer layer (xmpp4moz) takes care of blocking stanzas going
elsewhere than to the contact, and of mapping id attributes from local
to global and vice-versa.

The web page API is largely irrelevant and a library issue.  I would
concentrate more on capability and permission issues -- as it is, a
web page won't even save data to private XML storage since that would
happen over the user-to-server channel rather than the user-to-contact
channel.

-- 
Massimiliano Mirra
http://sameplace.cc
http://hyperstruct.net