> There's no such treatment. It's just a TCP connection, Since it's supposed to be a transparent object proxy, ideally it would handle connection problems, transparently. Maybe block for a while while it restarts the connection. I've yet to find a perfect network that never goes down, especially for long running scripts. :)
I'll dig around. On Wednesday, February 11, 2015 at 8:42:31 PM UTC-8, Tomer Filiba wrote: > > There's no such treatment. It's just a TCP connection, which is expected > to last four as long as you're working with it. There's also an option for > ssh tunneling, in which case ssh might be able to reconnect automatically, > but that's below RPyC. > > -tomer > On Feb 12, 2015 2:19 AM, "Brandon I" <[email protected] <javascript:>> > wrote: > >> Hello, >> >> I'm going to do some testing, but I thought I'd ask here first. >> >> How does rpyc handle things like intermittent connection problems? What >> if someone trips on a network cable for a while, then plugs it back in? >> Does rpyc gracefully handle the reconnect and possible ip change? >> >> --Brandon >> >> -- >> >> --- >> 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.
