Forget that HTTP stuff
A protocol-building toolkit
Unlike SOAP or XML-RPC, which at least began their careers on HTTP, BEEP goes back to the TCP foundations, and invites developers to use XML to build directly on TCP.
Multiple protocols, multiple URI types
Where SOAP and XML-RPC generally use HTTP and HTTP URIs, BEEP doesn't define any single URI. Using BEEP means that you're definining your own protocol, not merely layering over the existing HTTP protocol. This offers far more flexibility, something like a build-your-own-protocol kit.
SOAP can run over BEEP
One of the first bindings offered for BEEP is a binding for SOAP, making it possible to use Web Services with a technology often considered the IETF's answer to Web Services.
Previous Page <
> Next Page