Revision: 1147
http://omc.svn.sourceforge.net/omc/?rev=1147&view=rev
Author: bartw
Date: 2008-11-05 19:45:32 +0000 (Wed, 05 Nov 2008)
Log Message:
-----------
formatting changes
Modified Paths:
--------------
cmpi-bindings/trunk/README
Modified: cmpi-bindings/trunk/README
===================================================================
--- cmpi-bindings/trunk/README 2008-11-05 18:31:35 UTC (rev 1146)
+++ cmpi-bindings/trunk/README 2008-11-05 19:45:32 UTC (rev 1147)
@@ -1,7 +1,8 @@
Swig based CMPI bindings
------------------------
-This implements a CMPI-compliant provider interface for various languages via SWIG.
+This implements a CMPI-compliant provider interface for various languages
+via SWIG.
Currently supported languages
@@ -13,16 +14,19 @@
Implementation
--------------
-cmpi-bindings is implemented as a single CMPI-compliant provider (per supported language)
-that serves as a "multiplexer" to the instrumented language-specific providers.
+cmpi-bindings is implemented as a single CMPI-compliant provider (per
+supported language) that serves as a "multiplexer" to the instrumented
+language-specific providers.
-Using a python provider for class Py_Foo as an example, cmpi-bindings project provides a
-cmpi-compliant provider (libpyCmpiProvider.so) that will be registered with the cimom as
-the provider that handles Py_Foo requests. When libpyCmpiProvider gets the request, it
-will then forward it on to the python module that instruments the Py_Foo class.
+Using a python provider for class Py_Foo as an example, cmpi-bindings
+project provides a cmpi-compliant provider (libpyCmpiProvider.so) that
+will be registered with the cimom as the provider that handles Py_Foo
+requests. When libpyCmpiProvider gets the request, it will then forward
+it on to the python module that instruments the Py_Foo class.
-cmpi-bindings also provides supported-language-interfaces for the Provider Environment
-and BrokerCIMOMHandle, so that providers can make "up-calls" into the cimom.
+cmpi-bindings also provides supported-language-interfaces for the Provider
+Environment and BrokerCIMOMHandle, so that providers can make "up-calls"
+into the cimom.
For the stack discussion below, use the following 'type' abbreviations:
@@ -30,7 +34,8 @@
Python: py
Perl: pl
-The cmpi-bindings provider interfaces under CMPI consist of the following stack:
+The cmpi-bindings provider interfaces under CMPI consist of the following
+stack:
CIMOM
->
@@ -46,8 +51,8 @@
Build / Installation
--------------------
-The build scripts will only build the modules for which you have appropriate devel packages.
-It will skip any others.
+The build scripts will only build the modules for which you have appropriate
+devel packages. It will skip any others.
Requirements
------------
@@ -58,7 +63,8 @@
Build
-----
- From root of tarball's source tree, create a directory 'build' and move (cd) into that directory
+ From root of tarball's source tree, create a directory 'build' and move
+ (cd) into that directory
'cmake ..'
'make'
'sudo make install'
@@ -66,8 +72,9 @@
Test
----
For each language, there is a test/<language> directory.
- Within that directory, there should be test providers, scripts that use the test providers, and
- scripts to register the mofs and providers with cimoms.
+ Within that directory, there should be test providers, scripts that use
+ the test providers, and scripts to register the mofs and providers with
+ cimoms.
Language-specific documentation
@@ -80,6 +87,3 @@
-TODO
-----
-See separate TODO file
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
