I agree.
Maybe, as a 'starter straw man', Mickaël Rémond can outline the work
they've done in running XMPP 'all the way out to the client' at
ProcessOne (the makers of the kick-a** Erlang XMPP server ejabberd).
As one can see from another thread around here, the 0.3 version of the
server<->server XMPP protocol is being hashed out (with no less than
core XMPP team folks like Peter St. Andre contributing). The big
question I have is around this question of protobufs (I keep typing
'protobugs' - a Freudian slip? ;-) ) embedded in the XML. This imposes
an external dependency on what is otherwise a 'pure XML' format. I'm
sure Mickaël can say more about this. They are showing an update to
ejabberd that is obviously doing protobufs in Erlang. Their client is
written in Tcl/Tk so he can shed more light on whether they're
actually doing OT in the client (which would imply a protobufs
implementation written in Tcl) or, like the FedOne client and server,
the client is very 'dumb' (not doing OT) and just passing character
data back to the server.
One very intriguing thing that you'll find if you watch the ProcessOne
video is the usage of the XMPP 'discovery mechanism' ('disco') to
discover waves.
Cheers,
- Bill
On Oct 4, 2:48 pm, Joe Developer <[email protected]> wrote:
> On Mon, Oct 5, 2009 at 2:24 AM, Tad Glines <[email protected]> wrote:
>
> > On Sat, Oct 3, 2009 at 7:11 PM, elliottcable
> > <[email protected]> wrote:
>
> > > I should point out, for anybody following this, that the discussion
> > > has mostly moved to Wave… if you don’t have a Wave account, get in
> > > touch with me, and I can bring your voice into the discussion there.
>
> > I'm still waiting for my invite to be processed by Google so I'd
> > appreciate it if you could post a periodic update here.
>
> > I agree, I think that the discussion would be best served by having it in a
>
> widely accessible forum, such as this.
>
> From what I could see the discussion wave regarding this hasn't come very
> far.
> There seems to be interest in settling on an extension to XMPP, but there
> still lacks any work on outlining what such a protocol should encompass.
> This would probably be a good start.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Wave
Protocol" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en
-~----------~----~----~----~------~----~------~--~---
