Re: RPC-like behavior in a UDP server

I would suggest a better infrastructure. Split your program into pieces according to functionality:

To have a proxy, which handles UDP communication. It receives function calls (simply a UDP packet) from clients, and dispatch them to various servers accordingly.
Servers, those are the modules/files you talked about. They receives function calls relevant to them, process and returns.

This does gives you the ability to extend the capacity of your application freely.

Comment on Re: RPC-like behavior in a UDP server

Replies are listed 'Best First'.
Re^2: RPC-like behavior in a UDP server by rje (Deacon) on Jul 13, 2004 at 21:51 UTC
I'm a little confused at your terminology. When you say 'servers', do you mean that each module is a process, and communication between servers and proxy is via IPC or similar? (This sounds not unlike a POElike solution). Or are you simply saying that the proxy 'dispatches' calls to 'servers' by way of calling functions/methods on the appropriate packages/objects? (This sounds not unlike my and others' simple solutions). Either way (or some other way), thanks for the input. Rob	[reply]

Replies are listed 'Best First'.

Re^2: RPC-like behavior in a UDP server
by rje (Deacon) on Jul 13, 2004 at 21:51 UTC