I just wanted to add what I think it is needed in OpenHPI as an enhancement
to facilitate your situation.
What you need is a better use of the peer domain concept, which is part of
the spec, as a mechanism for redundancy in the HPI model. The problem is
that domains live in the same instance space in OpenHPI, so it doesn't buy
you much redundancy in its current implementation besides the way that
those peer domains may be connecting to the hardware.
An idea is, and hopefully something that can see the light of day next
year, to break domains into their own process spaces. The domain connection
manager would be in the client side, which could connect to mulitple
domains. Then, you could have peer domains running in separate systems. Now
you have better HPI data redundancy.
Saludos,
--Renier-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
