| 29 |
|
-------------------- |
| 30 |
|
|
| 31 |
|
One of the main topics of conversations that seems to have |
| 32 |
< |
come up time and again is how are the "clients" going to |
| 32 |
> |
come up time and again is how are the "hosts" going to |
| 33 |
|
communicate with the main system. CIM and WBEM provide a |
| 34 |
|
well defined standard of passing objects of data throughout |
| 35 |
|
a system. This means that the data undergoes no translation |
| 36 |
< |
at any stage, the "client" sources the data, wraps it in XML |
| 36 |
> |
at any stage, the "hosts" sources the data, wraps it in XML |
| 37 |
|
in the CIM Schema and passes it to the main system. This |
| 38 |
|
can then be passed so alter mechanisms, or can even be |
| 39 |
|
attached a CIM object that has a metaschema that allows |
| 125 |
|
About |
| 126 |
|
----- |
| 127 |
|
|
| 128 |
< |
This document was written by Alex Moore [ajm4@ukc.ac.uk] for |
| 129 |
< |
use by the team working on a 3rd year Computer Science |
| 130 |
< |
project called "i-scream". More details can be found on the |
| 131 |
< |
project website; |
| 128 |
> |
This document was written by Alex Moore for use by the team working on |
| 129 |
> |
a 3rd year Computer Science project called "i-scream". More details |
| 130 |
> |
can be found on the project website; |
| 131 |
|
|
| 132 |
< |
http://www.i-scream.org.uk |
| 132 |
> |
http://www.i-scream.org |
| 133 |
|
|
| 134 |
|
|
| 135 |
|
|
