HI Saurabh, I don't recall seeing that error, are you sure you're subclassing SlaveService? If you include some of your code here, I (or someone else) might be able to figure out what's wrong. It sounds like a minor config problem. . . I ran into a few snags when setting up my project with rpyc.
On Wednesday, June 13, 2012 5:13:59 PM UTC-4, Saurabh Pandey wrote: > > @Matt, when I tried to do that. It gives me a Attribute Error (VoidService > object has no attribute 'exposed_getmodule'). Did you face a similar > problem and how did you fix it? > > On Friday, May 25, 2012 9:32:32 AM UTC-7, Matt wrote: >> >> I ended up subclassing SlaveService and using rpyc.classic.connect(). I >> found the restrictions with the Service class to be too cumbersome and >> fortunately, all my code will be running inside my LAN so I don't need to >> worry about security as much. Eventually, I might switch over to SSH >> tunneling when I have my system debugged and deployed. >> >> On Wednesday, May 23, 2012 9:57:07 AM UTC-4, Daniel Honey wrote: >>> >>> No sorry, right now what I'm doing is just running a classic server >>> alongside my rpyc.Service. >>> >>> I'm only using the file upload method that the slave service provides >>> access to because its easier than using i/o streams or whatnot. >>> >>> Let me know if you figure anything out. >>> >>> On May 22, 3:10 pm, Matt <[email protected]> wrote: >>> > Just curious, did you figure out how to do this? I've been using >>> > rpyc.Service, but it >>> > looks like I really need to have full server access from my client, so >>> > I'm going to >>> > probably just switch to SlaveService i.e. the new version of rpyc >>> > classic. >>> > I'm going to play around with this a bit, if I figure it out soon, >>> > I'll add a comment >>> > here. >>> > >>> > On Apr 13, 4:37 am, Daniel Honey <[email protected]> wrote: >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > > I really want to use the upload function that slave service provides >>> > > as it seems to be the most direct way to transfer files. However >>> this >>> > > is only available under classic mode if you start a slave service. >>> > >>> > > I'd like to avoid creating a second arbitraryslaveserviceand instead >>> > > make the custom service im writing a slave service. >>> > >>> > > I tried to do the following: >>> > >>> > > class FooService(rpyc.SlaveService) >>> > > ..... >>> > >>> > > Then I start the threaded server with my FooService >>> > >>> > > But this does not work as I need to make a classic connection in >>> order >>> > > to use slave service's upload funtion. >>> > >>> > > Please advise, thanks. >> >>
