Hello Tomer, thanks for the quick und useful reply!
I can confirm the dictionary issues; that is not a show stopper though for what I am trying to do. Regarding the tunneling hints: This is great, looks like it is possible to embed rpyc in our existing communication scheme in a clean way. Nevertheless I have another question in this scope: I think I do not need a server when the connection already exists; How would I manage the access to multiple Services (bidirectional)? Are there some examples/hints in the documentation I was not able to find? Adrian Am Freitag, 8. August 2014 08:35:55 UTC+2 schrieb Tomer Filiba: > > str/bytes issues, dictionaries having different/incompatible methods, etc. > it's a different object model. > > as for tunneling rpyc over another protocol -- just implement your own > Stream or a Channel: > https://github.com/tomerfiliba/rpyc/blob/master/rpyc/core/stream.py#L21 > -- file-like transports > https://github.com/tomerfiliba/rpyc/blob/master/rpyc/core/channel.py#L13 > -- message-oriented transports > > a stream transfers bytes over some transport. a channel transfers > messages. if you protocol is already message oriented (e.g., HTTP) you can > directly implement a channel, but if it's stream like (e.g., TLS) it would > be easiest to implement as a stream. > > by the way, rpyc supports TLS (built in) and SSH tunneling using plumbum. > > > -tomer > > ----------------------------------------------------------------- > > *Tomer Filiba* > tomerfiliba.com <http://www.facebook.com/tomerfiliba> > <http://il.linkedin.com/in/tomerfiliba> > > > On Thu, Aug 7, 2014 at 8:22 PM, Adrian Genaid <[email protected] > <javascript:>> wrote: > >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- --- 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.
