OpenDAX Server
Mon, 06/25/2007 - 02:17 — phil
- Modules need to have a startup level of some kind. First level should be for modules that need to create tags, the second level for modules that are fairly critical but need the tags to be created before they are started. The last level would be for logging, alarm and HMI type modules. There could be many more levels.
- Some kind of locking mechanism on the tags needs to be created. We can't let one module delete another modules tags.
- I wonder if we need to add some kind of security to the server. I'm hesitant to do this but I suspect that it will be necessary at some point.
- We need a good portable way to determine the size that an individual message can be. Some systems have a #define and some may be able to read it at initialization time.
- The messaging and library functions need to be written to handle the STDIN / STDOUT pipes on each module.
- The opendax program should recognize that it's already running and either report that and exit or do something else useful. It could be used to stop or restart the system, or show status, list running modules, etc.