[OT] JMS-like event framework for Perl

["Michael A. Nachbaur" <mi...@nachbaur.com>]

Since today seems to be "The Day of the Off Topic(tm)", I thought I'd jump
in with my question.

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).

I could probably implement something like this to finish my project, but I'd
rather not do a one-off.  Does anyone know of anything that can accomodate
this functionality?  If I'm the first one trying to modularize this, what
features would you like to see?

Thank.

-man
Michael A Nachbaur
mike(at)nachbaur(dot)com

Re: [OT] JMS-like event framework for Perl

[Chris Winters <ch...@cwinters.com>]

* Michael A. Nachbaur (mike@nachbaur.com) [010310 14:25]:
> Since today seems to be "The Day of the Off Topic(tm)", I thought I'd jump
> in with my question.
> 
> 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).
> 
> I could probably implement something like this to finish my project, but I'd
> rather not do a one-off.  Does anyone know of anything that can accomodate
> this functionality?  If I'm the first one trying to modularize this, what
> features would you like to see?

Hi Michael,

Just to put another 2 cents in -- I have this exact same idea and
interest. I setup a project on Sourceforge for it
(sourceforge.net/projects/perlmq/) but haven't been able to put
together an initial ideas document yet. (Real life intrudes.) 

JMS seems to me a good model to follow as well. Why not use all that
hard work lots of people have already done? :-)

My initial thoughts were to base both the client and server around
POE. Messages would be standard objects but would have different types
of payloads: scalar, hash, array, object, XML document. SOAP would be
another way to request/send messages as well.

There is a mailing list on the sourceforge site to which we can move
all this discussion, if you'd like. (That way it will all be archived
in one place :-)

Thanks!

Chris

-- 
Chris Winters (chris@cwinters.com)
Building enterprise-capable snack solutions since 1988.

Re: [OT] JMS-like event framework for Perl

[Gunther Birznieks <gu...@extropia.com>]

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 (gunther.birznieks@extropia.com)
eXtropia - The Web Technology Company
http://www.extropia.com/

Re: [OT] JMS-like event framework for Perl

[Nathan Torkington <gn...@frii.com>]

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

Re: [OT] JMS-like event framework for Perl

[jeff saenz <je...@planetoid.net>]

Might be possible that soap is addressing messaging issues.

Nathan Torkington wrote:

> "Michael A. Nachbaur" wrote:
> >
> > Since today seems to be "The Day of the Off Topic(tm)", I thought I'd jump
> > in with my question.
> >
> > 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).
>
> I think there's an Event.pm, but you're probably after something like POE:
>
> http://www.perl.com/pub/2001/01/poe.html   <- intro and tutorial
> http://poe.perl.org/                       <- homepage (down?)
> http://poe.dyndns.org/                     <- Rocco's dialin machine
>
> Nat

--
Perl/Linux/Java Development
Resume: http://resumes.yahoo.com/undertheash/perljavalinux

Re: [OT] JMS-like event framework for Perl

[Nathan Torkington <gn...@frii.com>]

"Michael A. Nachbaur" wrote:
> 
> Since today seems to be "The Day of the Off Topic(tm)", I thought I'd jump
> in with my question.
> 
> 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).

I think there's an Event.pm, but you're probably after something like POE:

http://www.perl.com/pub/2001/01/poe.html   <- intro and tutorial
http://poe.perl.org/                       <- homepage (down?)
http://poe.dyndns.org/                     <- Rocco's dialin machine

Nat

Re: [OT] JMS-like event framework for Perl

[Matt Sergeant <ma...@sergeant.org>]

On Sat, 10 Mar 2001, Michael A. Nachbaur wrote:

> Since today seems to be "The Day of the Off Topic(tm)", I thought I'd jump
> in with my question.
> 
> 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).

POE works a bit like this.

-- 
<Matt/>

    /||    ** Founder and CTO  **  **   http://axkit.com/     **
   //||    **  AxKit.com Ltd   **  ** XML Application Serving **
  // ||    ** http://axkit.org **  ** XSLT, XPathScript, XSP  **
 // \\| // ** mod_perl news and resources: http://take23.org  **
     \\//
     //\\
    //  \\