messaging. I started out looking at the Infobus stuff, and even
wrote a few sample programs to play with that... and I think it
could be very useful.. But after I took that JMS class, I started
doing some google searching and found an in-memory JMS provider, and
now I think I'd favor the JMS approach even for intra-application (that is, one VM, non-distributed application) asynchronous messaging.
The loose coupling, and the resulting flexibility are what I like
about the messaging approach. Especially using topic based (pub/sub)
messaging. It's way cool in that the sender just send a message off
to the topic, without knowing who, or even how many, listeners there are. I'm envisioning a model for some of my apps here, where I declaratively configure various pub/sub listeners for my apps,
so I can rapidly and easily add / swap out / enhance the functionality
of my apps with minimal changes.
TTYL,
Phil
--
When the 1st Amendment no longer protects your voice.
And when the 4th Amendment no longer protects your privacy or your stuff.
Thank God we have the 2nd Amendment to tell our elected representatives that enough is enough.
It's time to put "... from my cold, dead hands" back where it belongs.
FREE AMERICA Vote Libertarian www.lp.org
_______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
