jabber as middleware taking more shape:

“All of the concepts and ideas above are just the start of a more formal specification for what JAM is. If nothing else, it is a description of a dream that I have for applications using Jabber. Of note, several people have raised a question about JAM replacing the current jabber:client protocol. This is not the goal of JAM. The end goal of JAM is to provide the necessary architecture and routing elements necessary for robust, efficient application communication. Jabber provides the basis for moving the data, JAM will provide the middleware semantics — it is up to the individual application to provide the content. In this way, JAM will be RPC agnostic. The payload it carries may be XML-RPC, SOAP or any other form of XML which an application cares to embed.”

Leave a Reply