Here are five use-cases developed on the "Jabber as middleware
developers" mail list, jamdev. There is also an early draft vision
paper. There isn't much content for either of these yet, but they
include a fresh transport perspective on developing collaborative
Using an IM system that is multi-protocol like Jabber as middleware
has interesting implications. One feature is dynamic application
discovery. Another is resource subscriptions as well as supporting
more traditional authentication, queuing and transactions.
-- -- Grant Bowman <email@example.com>
----- Forwarded message from firstname.lastname@example.org ----- Message: 1 Date: Fri, 30 Mar 2001 19:19:22 -0700 To: email@example.com From: firstname.lastname@example.org (Dave Smith) Subject: [JAMDEV] More docs
I'm have just posted another round of documentation to the website; of yet, I don't have a nice front page to index them all, so here's the direct links: * http://jam.jabber.org/docs/vision.html * http://jam.jabber.org/docs/supspec.html (empty) * http://jam.jabber.org/docs/usecase-summary.html
Most of you will probably find the use case summary the most interesting. It's the start of a detailed look at all the things applications will be able to do with JAM, as well as a ranking of difficulty and priority. Of note, most of the initial usecases will be high in priority and fairly difficult (since we have to come up with an entire protocol).
I also intend to write up a JAM roadmap so that we can start getting some dates designated for development. Hopefully, the use case summary, vision docs and roadmap will be completed by Monday.
As always, please feel free to ask questions about these docs. I would be highly suprised if anyone understood exactly what I was talking about simply from reading the use case descriptions. :)
----- End forwarded message -----
This archive was generated by hypermail 2.0.0 : Tue Aug 21 2001 - 17:58:03 PDT