next up previous contents
Next: Writing the client part Up: Example Previous: Example   Contents

Generating the PaCO++ code

Firstly, you write the IDL description of the server like in the figure [*].

Figure: The IDL server's description.
\begin{figure}\begin{verbatim}module Basic
{
interface Example
{
typedef s...
...ce<long> lseq;
void work_in(in lseq data_in);
};
};\end{verbatim}
\end{figure}

Then, you have, in an xml file, to describe the parallelism of your server. For example, you may want to say that the method work_in of the interface Example in the module Basic is parallel and the arg data_in is distributed using the GaBro distributed type. TO write this XML file, you have to follow the XML schema that is in the file interface.xsd in the IDL2Tool directory. The figure [*] shows the XML file.

Figure: The xml server's parallel description.
\begin{figure}\begin{verbatim}<Module>
<Name>Basic</Name>
<Interface>
<Name...
... </ReturnArgument>
</Method>
</Interface>
</Module>\end{verbatim}
\end{figure}

Finally, you have to use the PaCOIdlTool to generate the CORBA and PaCO++ stubs. This file needs four arguments :

Example : PaCOIdlTool interface.idl interface.xml omniORB4 0


next up previous contents
Next: Writing the client part Up: Example Previous: Example   Contents
2013-04-10