Re: ANN: Etiquette: a protocol construction tool
Miles Egan <[email protected]> Thu, 11 Sep 2003 21:48:48 -0700
| Newsgroups | gmane.lisp.clump |
|---|---|
| Message-ID | <1063342128.3884.3.camel@localhost> |
On Thu, 2003-09-11 at 21:27, Peter Seibel wrote: > > >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.) > > > > > > It's not used to actually move data, thank goodness. It's there for > > more for command channel / negotiation stuff. > > But the XML still goes on the wire? (As opposed to being input to some > BEEP tool which then generates code that implements the protocol.) Yeah. It's actually sent over the wire. It was actually an early attempt at a BEEP implementation that got me started with xmls. The BEEP test cases in the xmls test suite were some of the first ones added. This is why its xml use strikes me as somewhat gratuitous. The protocol data is somewhat heirarchical, but barely. miles _______________________________________________ Clump mailing list [email protected] http://manly.caddr.com/mailman/listinfo/clump
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQA/YVAvU4Jq/wH1PVERAkPFAJ9nuArYslA8LSoA6A9H05Cmcz/HqwCgtus/ DT+qOXL1oQKrCzhnmXJRlqk= =gYkQ -----END PGP SIGNATURE-----