[Ubermq-general] UberMQ 1.0

[James P. <jpa...@ya...>]

Welcome to UberMQ!  I'd like to take this opportunity to thank you guys
for joining my project, and welcome everyone to the group.

About the Project
=================

UberMQ is a project that I've been working on since January of this
year. Distributed messaging is a tremendously powerful metaphor, and
behind the simplicity lies a bevy of tradeoffs. The design of UberMQ is
ultimately very simple, but can be extended and modified in a variety
of ways to solve a multitude of messaging problems.

The entire product, as you know, is built on a one-to-many messaging
model, and the client API is the topic half of the JMS specification.
Most implementations get pub/sub horribly wrong - ubermq is not
perfect, but is much better than most that I've seen.

If you download the current 0.2 release and test out the sample code,
you'll see that UberMQ is a fast, stable, world-class pub/sub messaging
platforms that supports advanced features like clusering, durable
subscribers (in a usable way), and overflow management.

Getting to 1.0
==============

The 0.2 release that I built yesterday is very close to a
production-quality messaging system built on one-to-many messaging. In
order to get to a production quality 1.0 release, I think we need to
focus on the following unimplemented features:

  1. message selectors (the WHERE clauses you can attach to a
subscriber).
  2. reconnection (within clusters and without)

That's it. Most features are actually fully implemented!  

Part and parcel of a 1.0 release, though, is documentation and other
non-code deliverables:

  1. User's guide (how to install, sample code walkthroughs of
publishing and subscribing, how to use various features of the
product).
  2. Architectural overview (how its designed, how to customize the
Message Server)
  3. FAQ containing benchmarks and other reliability metrics 
  4. Sample code demonstrating various features.
  
Timetable
=========

The first thing I'd like everyone to do is to just send out a short
introduction to the list, so we all know who's who and who is actively
on the project. 

The next thing we should do is work out who'd like to work on what
tasks of the above listed. If someone would like to just focus on
writing sample code to try to break it (sending too fast, too many
connections, etc.) that would be a big help too. Hopefully by tomorrow
we'll be able to get people's names on the items above.  The two code
deliverables will need some architectural guidance from me to tell you
where to put things, but they are not too difficult, so please
volunteer if you're interested.

I'd like to get a 1.0 release out the door before Sept is out. I think
that's totally reasonable given the current stable state of the
project.  Also if you guys are in companies that use messaging, please
get the name of our product out there. Once we have some successful
installations to point to, we'll be well on our way. 

Conclusion
==========
Again, welcome to the UberMQ project. I hope you have a good time
working on this cool little distributed messaging product, and that we
can turn this into a sustainable gig.

James

__________________________________________________
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com