Re: [DotGNU]To What Degree Jabber?

[Peter Saint-Andre]

On Fri, 12 Apr 2002, Bradley M. Kuhn wrote:

> Meanwhile, our Chief Sysadmin (and general cool hacker) at the FSF, Paul
> Fisher, has suggested that we should look seriously at BEEP and APEX as
> well.  BEEP is defined by RFC's 3080 and 3081, and there is an IETF
> Working Group for APEX.
> 
> There is also an IETF draft for XML-RPC over BEEP, and for SOAP over BEEP.
> So, we don't have to abandon use of SOAP or XML-RPC if we choose to use
> BEEP.  APEX, as I understand it, would serve the same middleware level of
> XML-RPC, SOAP, and/or jabber:middleware.

Jabber actualy uses XML Streams for the transport layer itself.
This could be replaced by some other transport layer, and folks
have suggested BEEP in the past. You might be interested in the
XATP ("zapped") protocol that Jeremie Miller (creator of Jabber)
has been working on:

http://www.xatp.org/

Marshall Rose, who was heavily involved in both BEEP and APEX,
has recently shown a lot of interest in XATP and it may indeed
replace (or provide an alternative to) XML Streams as a transport
layer for Jabber data at some point.

Peter

--
Peter Saint-Andre
email+jabber: address@hidden
weblog: http://www.saint-andre.com/blog/