Hello, I am maintaining a django application that uses the older http-longpoll technique, yielding data back to the client. I would like coordinate that a bit with an additional message broker message
Problem: Have a client session/django app: fire off 2 synchronized threads sharing data. *Thread-one*: listens to a dbms for notifications and writes a *shared_buffer*[] when data arrives and *Thread-two*: listens to a message broker for a message, and flushes (yields) the *shared_buffer*[] when an appropriate message arrives to the broker. *My question is*: should I be configuring WSGIDaemonProcess or should I be in embedded mode? I want to avoid having the *shared_buffer*[], shared between two web-client sessions, which I believe will be in the same thread pool if I configure in WSGIDaemon mode. Thanks, Jeff -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
