Hi!
The first problem I saw with Pyro Event Server is that it seems to me
too complex for the task.
Django uses PyDispatcher as the in-process event subsystem. In order to
make the event objects network-dispatchable, the only thing that should
be done is to find a way to serialize events somehow,
Spread should work nicely but I wouldn't ditch Pyro that easily either.
Pyro works extremely well for this. I know because we've been using
since it 2001 to implement many kinds of distributed processes
including one similar to what you're describing. Our event management
system consists of a d
Hi.
I have the very first working prototype. Now it works over UDP, using
asyncore library. UDP is unreliable under heavy load, so I don't
recommend using it in production. However, my dispatch system abstracts
event dispatching from the transport, so any suitable transport can be
plugged in. It's
I think this is a a whole a very nice idea.
Max Derkachev wrote:
> 1. Events should be routed using IP protocol. [...]
> 2. There should be a master server (started as a standalone daemon).
> 3. Every Django instance that needs to be aware of application-wide
> events [...]
If you are not afte
Hello all.
Since Django apps tend to function in multi-process environments (both
in mod_python and FastCGI modes), I've faced a necessity to route
events between processes that execute Django application instances.
Django uses PyDispatcher to dispatch events, but it's a single-process
and can not
