Re: ANN: Etiquette: a protocol construction tool

Miles Egan <[email protected]> writes:

> Eugene Zaikonnikov wrote:
> 
> > So far I've just skimmed through BEEP Core and CAP specifications, but
> >
> >it looks like BEEP protocols have broader scope. They seem to go much
> >deeper into defining message data types (Etiquette protocols do not
> >define content representation), and use several transmission channels
> >for communication. Introduction of secure transport support and
> >sibling protocols (which are similar to BEEP channels) to Etiquette
> >could in theory permit implementation of the BEEP protocols, but my
> >initial feeling is that the underlying models are too different to be
> >mapped naturally.
> >

> Ok. Thanks for the info. My impression of beep so far is that it's
> basically a useful and reasonable idea but that its use of XML is
> somewhat gratuitous.

Does BEEP use XML as a data transfer format or as a descriptor
language for defining protocols. (I read some of the O'Reilly book on
BEEP a while back but don't remember where, if at all, they used XML
in that version.)

-Peter

-- 
Peter Seibel                                      [email protected]

         Lisp is the red pill. -- John Fraser, comp.lang.lisp