C integrated RPC

[andrew babanin]

>>> 2009/1/21 Joel Sherrill <joel.sherrill@oarcorp.com>:
>
> Is the marshalling and encoding based upon anything
> standard?
>
> Does it support RPC's across heterogeneous hosts?

Data that should be send through the net is packed using my own method.
It is rather simple, but marshaling is made automatically, in C code, generated
by wrapper compiler. This data format supports so called __in and __out data,
so as the system (__in and __out midificators used with function paramters).
So the system can control which data should be send to the server and which
data should be retrived from the server.

CRPC can forward calls for remote functions, also remote calls can be
done from another
servers, like apache (from apache module). As it uses TCP/IP it will
work with heterogeneous
hosts.

>
> I think so.  The run-time assumes POSIX threads and BSD sockets
> and (I assume) POSIX mutex for the locking.

But there might be some problems running treaded application yet) I am
working on it.

> Depending on how things go with the merge, it probably makes
> sense to switch to the gcc portability wrappers for threading
> and mutexes.  But it is up to others on merging.  I was just
> trying to clarify the run-time requirements. :)
>

To see how wrapper-compiles extends there is two files in attach, the source
and temporary compiler file after language extension.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: clnt.c
Type: text/x-c
Size: 1403 bytes
Desc: not available
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20090121/d5f06dab/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: r6vShf.i
Type: application/octet-stream
Size: 10626 bytes
Desc: not available
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20090121/d5f06dab/attachment.obj>