[Twisted-Python] Alarm collection and display system?

[Gangadhar NPK]

So this is a subscription model, with a single point aggregator right ?
The *proxy* aggregates the messages from the producers, while the
consumers subscribe with the proxy regarding the message(s) they are
interested in and the messages are pushed to them by the proxy.

On 5/21/05, Brett Viren <bv at bnl.gov> wrote:
> Gangadhar NPK <npk.gangadhar at gmail.com> writes:
> 
> > Hi Brett,
> > Let me restate the problem (in an oversimplified way, sorry about that)
> >  - the ability for disparate systems scattered across the network to
> > push messages to interested consumers distributed across the network
> > in a (near) real-time fashion.
> > Did I get it right ?
> 
> Yep, exactly.
> 
> > If that is the case, then as Glyph suggested, keep your consumers
> > available to get messages from the producers.
> 
> Yes, sage advice.
> 
> > As an aside, can you share how you plan to go about creating a
> > distributed subscription service - I mean, how do the consumers
> > provide information for producers to know about the subscription
> > status.
> 
> The idea was to *not* distribute the subscription service, but rather
> to centralize it into a single, well known, server, (actually, a
> "proxy server" might be the more proper term).  All producers deliver
> messages to this single proxy which then delivers them to any
> connected consumers.  The producers don't know or care who the
> consumers are.  Very simple (I hope).
> 
> My first choice would be to use XML-RPC for the protocol.  Since there
> are a plethora of XML-RPC implementations it should make it easier to
> glue in this protocol to the disparate producers.
> 
> -Brett.
>