>From what I understand, state information for web apps is usually stored in databases. What are you trying to do, if you don't mind me asking?
On Feb 12, 10:09 am, till amon <[email protected]> wrote: > Hello all, > and apologies upfront for going to be vague. > > i'm toying with mod_wsgi for a couple of days now and still am > somewhat struck when it comes to threading semantics - especially how > to share state between processes. > > the current setup is like this : > WSGIDaemonProcess daemon_group processes=1 threads=15 > > Which is working fine as long as there is only one process. > now to the vague part : if one wants to have other processes serving > different scripts , what would be the cleanest way to share state > among them if responsiveness was the main concern ? > > (starting a 16th thread to wait for a unix pipe or socket does not > seem to work - by design i guess ? ) -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
