NobleNet RPC and RPCGEN |
||||||||||||||||||||||||||||||||||||||||||||||||
|
Competitive Comparison: NobleNet RPC and RPCGEN Ease of Use: NobleNet RPC is very easy to use and only requires 'C' application programming expertise while RPCGEN is very cryptic and requires low-level communications expertise. Documentation: NobleNet RPC user documentation is clear and concise while RPCGEN's is poor. RPC Coding: NobleNet RPC auto-generates RPC code while RPCGEN requires manual RPC coding. NobleNet RPC can read applications header files to get structure, typedef and enum information while RPCGEN requires the programmer to recode this information. Development Time: NobleNet RPC is noted to cut development time by 10x versus RPCGEN. NobleNet RPC has convenience routines for 'fast prototyping' while RPCGEN has no such feature. Performance: NobleNet RPC data transfer has been cited at 4.5 to 20 times faster than RPCGEN Output: NobleNet RPC outputs clear, commented, and easy-to-read 'C' source code where RPCGEN's 'C' output is very hard to read. Data Structure Support: NobleNet RPC has extended the XDR Layer to handle complex data types to handle 'pointer to pointer', 'pointer to array', and 'pointer to array of pointers'. RPCGEN does not support complex data structures.
|
Did you know: that NC Labs JaRPC libraries and development system are compatible with the NobleNet RPC standard? |
Copyright NC Laboratories Inc, 1998, 1999, 2000 all rights reserved. Legal Statement