[news.eclipse.technology.ecomm] Re: What about SIP/SIMPLE?

[Scott Lewis <slewis@xxxxxxxxxxxxx>]

Hi John,

John F. Patterson wrote:
> Do you envision the possibility of SIP/SIMPLE implementations of your 
> platform?

Absolutely.  The general approach is:  define a small (3ish) set of 
plugins that expose generic apis...for identity/authentication, pt2pt 
and multipoint messaging, and a component api.  Underneath each api, 
provide implementations to support existing protocols...e.g. SIP/SIMPLE, 
XMPP, JMS, etc.  To allow for client-side interoperability.

You actually caught me working on an implementation of the messaging API 
to support communication via XMPP (Jabber protocol).  I would very much 
like to include SIMPLE/SIP in that initial set of supported messaging 
implementations, so that plugin developers could use ecomm to easily 
talk with SI* servers and client.

> Do you know of any reasons why this would be precluded?  Or, is it too 
> early to say one way or the other?

No, it certainly wouldn't/won't be precluded.  I'm realizing part of the 
trick of the design of such generic apis is to make them sufficiently 
abstract to handle these various messaging protocols (and their various 
ways of doing security, different features, etc.) while still providing 
an API that is useful at the application level.  I think we've got 
something that is a good mix of abstract enough to handle multiple 
protocols while still providing some added value to applications/plugins 
that use such apis.

Thanks for the comments.  If you know of good open source and java 
implementations of SIMPLE/SIP please let us know.

Scott