| Product: Distinct RPC for Java | Topic: General | Last updated: 3/26/2008 |
| |
| Q.: When I try to run jrpcgen on my x file or one of your sample files, I get the following error message: Jrpcgen: "cl/C/EP/nologo" failed: CreateProcess |
A.: For preprocessing, you must have a C/C++ compiler installed. If a C compiler is not required then you can use
java Jrpcgen -n myfile.x
On a Unix System you must specify where the compiler resides. The correct syntax is:
java Jrpcgen -c /usr/ccs/lib/cpp myfile.x
Options related to preprocessors:
-n
Do not run the C/C++ preprocessor before translating the ".x" file. This option is useful when you do not have a C compiler installed and you want to translate a file that does not contain preprocessor directives.
-c C-preprocessor
Specifies the name of the C/C++ preprocessor to be used. The default is "cl/C /EP /nologo" (which is valid for Windows systems). Specify the command line if you are using a different preprocessor (for example, "/usr/ccs/lib/cpp" on Solaris systems).
|
| |
Do you find this information useful ?  Yes No Not Sure |
|
| Product: Distinct RPC for Java | Topic: General | Last updated: 3/26/2008 |
| |
| Q.: When is Distinct ONC RPC/XDR for Java a better choice than RMI and Why? |
A.: Distinct ONC RPC/XDR for Java is the clear winner when any of the following is important:
* Whenever you need to interoperate with C or C++
* When compatibility with legacy systems is required
* When ease of programming is an issue. RPC is smaller and much easier to program with compared with CORBA based programs.
* When your distributed application is requesting the execution of functions on a remote system and speed is an issue.
A typical procedure call in a distributed application consists of a function call issued by the client to a server. The server executes the function and returns the result to the client. In most cases the call itself and the returned results require the transmission of just a few packages, with the workload being the processing done on the server side.
We have taken some time to write test applications in both Distinct’s Java RPC and RMI to illustrate the speed issue. In all our tests Distinct ONC RPC/XDR for Java resulted 40% to 50% faster than RMI. We are making available two of the test programs used in this analysis.
|
| |
| Do you find this information useful ? Yes No Not Sure |
|
| Product: Distinct RPC for Java | Topic: General | Last updated: 3/31/2008 |
| |
| Q.: Which RFCs does the Distinct ONC RPC/XDR for Java support? |
| A.: RFCs 1831 and 1832 are supported. |
| |
| Do you find this information useful ? Yes No Not Sure |
|
| Product: Distinct RPC for Java | Topic: General | Last updated: 3/26/2008 |
| |
| Q.: Will Distinct ONC RPC/XDR for Java work on any Java platform? |
| A.: Yes, Distinct ONC RPC/XDR for Java continues to have 100% Pure Java certification from Sun Microsystems. This means that it will work on any fully compliant Java platform. |
| |
| Do you find this information useful ? Yes No Not Sure |
|
| Product: Distinct RPC for Java | Topic: General | Last updated: 3/26/2008 |
| |
| Q.: Will the Distinct version of rpcgen allow me to use C-style remote procedure signatures (like the Sun -N command-line option)? |
| A.: Yes, this feature is supported as of version 3.0. |
| |
| Do you find this information useful ? Yes No Not Sure |
|
