[Design] Chandler Agent Framework

[Nitin Borwankar]

petite_abeille wrote:

> On Friday, Dec 6, 2002, at 11:33 Europe/Zurich, Blake Ramsdell wrote:
>
>> I think in a prior message, Michael McLay also suggested the use of BEEP
>> as a generic Chandler protocol underpinning, just so you don't think I'm
>> a kook...
>
>
> Well, that would make three of us ;-)
>
> And, oh surprise, there are at least three relevant implementations 
> for Chandler to leverage:
>
> - BEEPy
>
> - beepcore-ruby
>
> - beepcore-c
>
> http://www.beepcore.org/beepcore/projects.jsp
>
> In short, BEEP is popular enough and well documented.
>
> http://www.beepcore.org/beepcore/specsdocs.jsp
>
> 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.

Nitin Borwankar.

-- 
The more idiot-proof you make it, the smarter the idiots get.

Nitin Borwankar
nitin@borwankar.com


>
> Cheers,
>
> PA.
>
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design