Although SOAP::Lite interfaces with SMTP and POP3, I don't know if
SOAP::Lite really qualifies to be in the same class as products like JMS,
Neon, or Microsoft MSMQ.
However, I think the description of what the author is interested in is a
bit vague. The words seem to indicate that he would be satisfied by setting
up a SOAP service on an HTTP server that listens to calls made to it (the
events) and then runs.
This is a simpler model and does not really describe publish/subscribe as
being a feature he wants. That is, to me, IMHO ...
Publish/subscribe entails a lot of headaches about allowing multiple
subscribers (consumers of data), maintaining the integrity of those
messages, and making sure that all subscribers have a fair chance to get
them. In larger environments the idea behind messaging is that you
sacrifice speed for reliability of having a central queueing mechanism that
may or may not be backed up by a persistent storage and that can notify
clients that are subscribed in sort-of real time that a new message exists
on the queue (without having to poll).
And it doesn't sound like this user needs that. Also has not made clear
what the relationship is between the event-driven objects. If the client is
always requesting from the server or if the server needs to "call back" to
the client to notify the client that something has occured. The former is
obvious and easy with SOAP while the later is somewhat less trivial.
POE seems more interesting, but is also not precisely publish/subscribe. It
seems a bit more generic than that. Again, not quite the same as JMS, but
something like it could be built from POE it seems.
The thing that would be interesting to me is a more detailed description of
what is needed. What features of JMS specifically are interesting to the
original poster. Perhaps a project written on top of SOAP::Lite or POE
would be in order. Or perhaps maybe the problem is just simpler than it's
made out to be by asking for JMS features.
At 09:25 AM 3/11/2001 +1300, Nathan Torkington wrote:
>jeff saenz wrote:
> > Might be possible that soap is addressing messaging issues.
>
> > > > Is there a event messaging framework available for Perl, similar to
> JMS?
> > > > I'd like to be able to have an object registered as a handler for
> certain
> > > > "events", and have perl code throw those events causing the object
> to be
> > > > run automatically (publish / subscribe model).
>
>You're right, SOAP::Lite can do these things (and more). I was hallucinating,
>thinking that you wanted to write a program in an event-driven style.
>
>http://www.soaplite.com/
>http://guide.soaplite.com/
>
>Nat
__________________________________________________
Gunther Birznieks ([EMAIL PROTECTED])
eXtropia - The Web Technology Company
http://www.extropia.com/
