Hello!
As I can see now, OpenHPI daemon and plug-ins has no knowledge about
domain they are belong to.
The domain information is defined in openhpiclient.conf, but not in
openhpi.conf.
I've found that daemon creates only default domain now with id = 0.
Issue 1:
saHpiDomainInfoGet returns information about domain with id = 0, but
not
with to which session was opened.
Shall we override DomainInfoT.DomainId after retriveing information
from
daemon but before passing it
to HPI User?
Issue 2:
DomainId in DAT Alarms is also set to 0.
Issue 3:
DomainEventT.DomainId - the same issue
Question 1:
What about DRT architecture? Is it working now?
Question 2:
What about status of hpi_shell "-n" key now?
We have tested it with trunk - it does not work.
Shall we remove it because it interferes with current multi-domain
architecture?
Anton Pak
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
