[Council] Re: [Design] Chandler Agent Framework (fwd)

Peter Saint-Andre stpeter at jabber.org
Fri Dec 6 17:41:54 CST 2002


Hmm, does this count towards JEP-0009?

BTW, interesting thread here:

http://lists.osafoundation.org/pipermail/design/2002-December/001280.html

Follow the whole thing, it gets rather interesting. :)

Peter

--
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.php

---------- Forwarded message ----------
Date: Fri, 6 Dec 2002 15:28:15 -0800
From: Dave Winer <dave at userland.com>
To: Peter Saint-Andre <stpeter at jabber.org>
Cc: radio-dev at yahoogroups.com
Subject: Re: [Design] Chandler Agent Framework

FYI, we're transporting XML-RPC serialized calls over Jabber and AIM with
good results. This is as was discussed at JabberCon in 2001. It works. ;->

Dave


----- Original Message -----
From: "Peter Saint-Andre" <stpeter at jabber.org>
To: <design at osafoundation.org>
Sent: Friday, December 06, 2002 12:36 PM
Subject: Re: [Design] Chandler Agent Framework


> On Fri, 6 Dec 2002, Nitin Borwankar wrote:
>
> > petite_abeille wrote:
> >
> > > On Friday, Dec 6, 2002, at 11:33 Europe/Zurich, Blake Ramsdell wrote:
> > >
> > > Plus its simple, straightforward and lightweight. Adjectives that
> > > don't spring to mind when describing Jabber...
> >
> > Also, BEEP is on the IETF Standards track.
> > APEX an "application layer" on top of BEEP is worth looking at as well.
>
> Once again I reiterate that I am not pushing for Jabber as the solution to
> everything -- it was built for IM and presence and is only slowly moving
> beyond that (e.g., to transport RPC etc.). And I admit I'm biased in favor
> of Jabber. However, I think it's a stretch to say that the Jabber protocol
> (which we've started calling XMPP, short for Extensible Messaging and
> Presence Protocol) is more complex and heavier than BEEP. Further, there
> is quite a bit of IETF activity around it now:
>
> http://www.jabber.org/ietf/
>
> Certainly it may be that BEEP is the best solution for Chandler's needs.
> But over at the Jabber Software Foundation we've defined some protocols
> that may be of use for Chandler's agents framework, including a general
> data description format (jabber:x:data, defined in JEP-0004) that is
> something like HTML forms for Jabber (currently being used for workflow
> systems, service configuration, etc.) and the beginnings of a generalized
> publish-subscribe protocol for real-time event notification. These
> protocols are not in our Internet-Drafts because they are not necessary to
> meet the requirements of RFC 2779, but there is a lot of protocol ferment
> in the Jabber community and we certainly welcome contributions from people
> who would like to propose new extensions. Information about our process is
> here:
>
> http://www.jabber.org/jeps/
>
> Finally, I'm curious to hear what the perceived "eccentricities" are with
> regard to Jabber/XMPP. Feel free to contact me off-list about this, since
> it may be off-topic here.
>
> Peter
>
> --
> Peter Saint-Andre
> Jabber Software Foundation
> http://www.jabber.org/people/stpeter.php
>
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design




More information about the Council mailing list