suppose you're working in synchronous mode: the client initiates a request on the server and waits for the reponse. while the client waits, it actually becomes a "mini server" that can process requests from the server. in other words, the protocol itself is symmetric: the only difference between a client and a server is who connects to whom (in the socket level).
if you're working in async mode, you should either poll the connection every so often, or use the BgServingThread ( http://rpyc.sourceforge.net/api/utils_classic.html#rpyc.utils.helpers.BgServingThread) which simply processes requests in the background. hope this gets you going -tomer ----------------------------------------------------------------- *Tomer Filiba* tomerfiliba.com <http://www.facebook.com/tomerfiliba> <http://il.linkedin.com/in/tomerfiliba> On Thu, Jan 17, 2013 at 4:56 PM, <[email protected]> wrote: > > Lets say I run a server S and a client C. I understand that C can call S > anytime and get data back using RPC. How does RPYC implement the call from > server to client, Especially on windows? Is it done using polling / > threading? Perhaps someone who understands this can drop me a few lines and > a pointer where I can read more. > > Thanks. >
