I think it is reasonable to make generic implementation of IPC box a part of libc so that to provide a single RPC manner around the overall system.
> Hi all, > I spent many time on IDL design, I found some architecture leaks (ticket > can be corrupted and server may take insecure request from anybody). > I decide to reimplement liborb stuff, this will affect libc. > As you know, all calls going via RPC, that mean we need to have ORB > related functions and structures to be included in libc, also some > generic implementation of ipcbox should be also included. > My ORB part in libc doing the following things: > - serialization/deserialization > - verify types/functions due to the generated ORB environment (context) > - invoke IPC related parts (tickets, ipcbox_msg_t) to generated > functions. > I guess that we need to include libipcV to libc as a generic > implementation of ipc box, if you will need to change this, you may do > it within your server code. > > Any comments ? > > PS all changes will be made within my sandbox, and I will merge it while > all parts will be ready to use. There are many bugs and architecture > issues. IDL/ORB is very difficult task ;) Best regards, Dmitry Gromada _______________________________________________ Jarios-dev mailing list [email protected] http://lists.jarios.org/cgi-bin/mailman/listinfo/jarios-dev
