RFC3288 describes how to do SOAP over BEEP, and Joe Gregorio points to IBM Alphaworks’ implementation, BeepLite. I wonder how this performs? Maybe a custom BEEP transport for Systinet’s Java Server would allow for some nice comparative studies …
RFC3288 describes how to do SOAP over BEEP, and Joe Gregorio points to IBM Alphaworks’ implementation, BeepLite. I wonder how this performs? Maybe a custom BEEP transport for Systinet’s Java Server would allow for some nice comparative studies …
Performance? Excellent question! I bet it performs like a dog, since it’s doing in three layers (SOAP, BEEP, application interface) what most application layer protocols do in one. It could be improved by building a combined SOAP/BEEP layer, but I’d bet money that it’d never do as well, in the general case, as a single dedicated-to-a-single-application application protocol.