Re: [Mod-pubsub-developer] Non-blocking publishing in Python

[<mod...@li...>]

Adam:

Is your information current?  I was under the impression that a 
streaming design was now in place for Active MQ and/or xmlBlaster's HTTP 
capabilities.  But that's probably wrong, I am vaguely remembering a 
feeling I got while skimming some docs a while back.

:-)

Either/both of these projects support dynamic topic creation and some of 
the core requirements to achieve REST client access characteristics.

I think mod-pubsub should consider layering itself onto these two quite 
popular, and quite active, MOM projecs.  Think "REST pubsub module" for 
MOM instead of for Apache.  The client-access characteristics that would 
emerge could act as a motivator for the MOM community to adopt REST 
architectural principles.  The current mod-pubsub server could/should 
interact well with these modules, allowing it to become a "subsidiary" 
or "proxy" event notification server, giving developers the choice of 
using the lightweight mod-pubsub solution in contexts where the 
full-blown MOM solution is inappropriate, yet connecting the two, or 
switching to the MOM solution, without ever changing APIs.

Alright, I'm just blowing hot air, but it was fun.

A.

mod...@li... wrote:

>A. wrote:
>
>  
>
>>>In the interest of strengthening everyone's knowledge base, what did you
>>>compare against and what were your concerns?  I've noticed that
>>>xmlBlaster and Activ MQ both offer HTTP oriented methodologies for
>>>asynchronous notification.  But I am not sure how robust they are, nor
>>>how native/central to the design they are, nor how well they work in
>>>javascript contexts.
>>>      
>>>
>
>  
>