[
Lists Home |
Date Index |
Thread Index
]
rsalz@datapower.com (Rich Salz) writes:
>BEEP. A real application protocol designed by someone who knows
>networking.
Hey, I get to agree with Rich!
BEEP is very impressive generally, and makes far more sense to me than
SOAP (over HTTP or not) for use as a general-purpose network protocol
framework.
Interestingly, BEEP also excludes the DOCTYPE declaration and the XML
declaration in content of type application/beep+xml - but since that's
only used to set up conversations, not to conduct them, it isn't nearly
as severe a restriction.
BEEP seems to me like the natural alternative for situations where XML
over HTTP (minus the envelope) isn't enough. SOAP feels to me like a
(peculiar) message format, while BEEP is a toolkit for sending your own
message formats, whatever they might be. It uses XML and its own
vocabulary where it's convenient, and then gets out of the way and lets
you send whatever you like.
Cool stuff, definitely. Not that I expect the world to suddenly change,
but good stuff is out there.
More info at:
http://www.beepcore.org/
There's also an O'Reilly book, BEEP: The Definitive Guide, by Marshall
Rose, creator of the spec. It's as much about implementing BEEP as
using it, but it's good reading.
--
Simon St.Laurent
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!
http://simonstl.com -- http://monasticxml.org
|
