Hello, I am having a look on RPyC in order to enable secure python rpc in a client/server application. As of now, the results are quite promising.
I was even able to use a Service (not the classic service) served in Python 3.3 from IronPython. Your documentation tells it is not possible to communicate between python3 and python2 interpreters (IronPython is 2.7); what will not work in such scenario? One thing I was not yet able to figure out is whether I could tunnel the RPyC communication through the existing client/server connection. Could I somehow fake a socket object and feed the messages from our internal protocol into RPyC/wrap sending messages accordingly? The communication scheme of the client/server application is based on an event queue. Has someone done something like that before? Is it a reasonable approach? Thanks for hints! Adrian Genaid -- --- You received this message because you are subscribed to the Google Groups "rpyc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
