http://www.opendax.org/project/issues en http://www.opendax.org/node/56 I need to add the capability to handle messages that come without being requested. This would need to be for callbacks, command messages, wakeups etc. Wed, 21 Nov 2007 15:15:52 -0600 http://www.opendax.org/node/56 OpenDAX Server http://www.opendax.org/node/76 Right now opendax simply sends a SIGTERM to all of it's children, cleans up the message queue and then bails. It really should check that all the modules are dead and send SIGKILLs to all the ones that persist, then clean up the queue and exit. I've seen the modbus module stay running a couple of times. In the grand scheme of things it isn't that major but it looks cheesy to still have modules hanging around after we are gone. Fri, 15 Feb 2008 13:09:31 -0600 http://www.opendax.org/node/76 OpenDAX Server http://www.opendax.org/node/60 Need for modules to be able to register for notification if a tag changes. A message will be sent to these modules anytime the value of the tag is changes. Sun, 23 Dec 2007 21:21:49 -0600 http://www.opendax.org/node/60 OpenDAX Server http://www.opendax.org/node/37 When the library messaging functions are waiting for a response from the core there is a potential to block forever if the message is lost. I guess we could send a wakeup message of some kind or use signals or maybe break the whole thing off into a thread like the core. Thu, 27 Sep 2007 21:44:08 -0500 http://www.opendax.org/node/37 OpenDAX Server