[JDEV] Jabber as COM/DCOM replacement for linux.

[ogeorge at lor.jeremie.com]

Let's evolve jabber, not split it up......

> > I'd like to second Dizzy's suggestion of creating a jabber:middleware
> > protocol. The jabber:client protocol is great for IM, but JAM
> > (Jabber-as-Middleware) is different enough to merit some wide-open
> > thinking about the protocols involved.
> 
> Well, after chatting with Dizzy a little, I completely agree.  I was
> leary at first since we'd have to reimplement a lot of the jabber:client
> functionality.  However, he convinced me that it needed to be redone in
> a new protocol, as the current method may not be robust enough for
> middleware.

I'm sure you are right but i'd like to hear the arguement anyhow.

I'd like to see this as an evolution of jabber actually.  Transports are 
distributed objects and should be accessed as such, clients should interface 
these transports by methods.  the current use of iq/set namespaces seems silly 
when compared to using an XMLRPC type approach.

*** COMMENT ON THIS PLEASE, THIS IS THE INTERESTING BIT ***

Plus with the ability for thin clients (especially across internet) to 
communicate directly to these objects by XMLRPC style protocols... it just 
should be like this.

are there any jabber developers listening who can comment on these ignorant, 
richeous comments.  i'm not a gun jabber coder, i'm keen for other opinions.

cheers, Oliver.