10-21-04 12:48 PM
In article <fe6eb44f.0410210421.1d9eec3@posting.google.com>,
james@james-pascoe.com (James Pascoe) wrote:
> I can't use an exisiting RPC toolkit for two reasons:
>
> i) it will introduce a library dependency into my code
Why? There must be several RPC libraries available, so you can use any
of them.
> ii) the complexity is probably unnecessary
If you're trying to do everything that an RPC library does, the
complexity has to reside somewhere. The fact that you had to post here
indicates that it's complex.
>
> So, I am rolling my own. Now, pretty much all of the reference
> material centers around well known toolkits such as Sun RPC, so I was
> wondering if anyone had any general advice on this particularly with
> regard to the following:
>
> i) marshalling and unmarshalling data - particularly with reference
> to
> byte-order and passing data between architectures that implement
> the same
> types differently
Can you use an existing XDR library? That will allow you to marshall
the data into a buffer that you can then write().
> ii) general RPC protocol advice
Send a query and wait for the reply.
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
[ Post a follow-up to this message ]
|