Very Computer

by **Christophe Beljouani (Toulou** » Fri, 31 Jan 1997 04:00:00

Hi there !

I have the following problem using RPC. With rpcgen , I built a client
and a server. The client use a remote function and get a structure.
This structure is a linked one:

struct res
{
int x;
struct res *next;

Quote:}

The problem I have is that the function I use can send back
a linked structure which can contain a "big" number of element.
This code works basically with minus than 1000 elements and start
to fail with more elements. I suspect a problem with the size of
the TPC (the used protocol) packets but ... nothing in the rpcgen
man pages mention such a limitation ...

If someone has an idea, please, let me know.

Thanks,
Christophe

by **Ricardo Corr** » Sat, 01 Feb 1997 04:00:00

Quote:Beljouani (Toulouse)) writes:

|>
|> Hi there !
|>
|> I have the following problem using RPC. With rpcgen , I built a client
|> and a server. The client use a remote function and get a structure.
|> This structure is a linked one:
|>
|> struct res
|> {
|> int x;
|> struct res *next;
|> }
|>
|> The problem I have is that the function I use can send back
|> a linked structure which can contain a "big" number of element.
|> This code works basically with minus than 1000 elements and start
|> to fail with more elements. I suspect a problem with the size of
|> the TPC (the used protocol) packets but ... nothing in the rpcgen
|> man pages mention such a limitation ...
|>
|> If someone has an idea, please, let me know.
|>
|> Thanks,
|> Christophe
|>
|>
|>
|>
|>
|>
I do not understand why you would ever want to send a pointer
( to a local memory address ) over the network, it does not mean anything
at the other end, and might only work for testing purposes if both server
and client are running on the same machine.

Try sending only
struct res
{
int x;

Quote:}

and create a new list at destination as the structs arrive.

--

Very Computer

RPC problem

RPC problem

RPC problem