Has anyone considered the concept of running two copies of misterhouse simultaneously where the second copy has most all of the common code disabled and is used to manage slow polling processes?
While reading this thread (yes I’m a bit behind):
I started to wonder about all the dozen or so “external” daemons and cron jobs that misterhouse users must be using. I like being able to manage these inside some framework where I can selectively enable/disable as well as keep tabs on the running processes. In general is there a problem with a copy of misterhouse that routinely has large pauses (i.e. broken code, memory leaks, etc.)? I suppose xPL could be used to pass object state changes between the two misterhouse instances.