zero deploy has several requirements (which i don't remember now) that practically mean it only works for classic mode. theoretically you can work around them but i haven't tried to.
anyway, zero deploy doesn't really makes sense with a custom service, since custom services are usually "well known", e.g., your clients know that machines1 is your database. zero deploy is mostly for debugging/testing purposes, where you may not want an rpyc daemon running all the time. -tomer ----------------------------------------------------------------- *Tomer Filiba* tomerfiliba.com <http://www.facebook.com/tomerfiliba> <http://il.linkedin.com/in/tomerfiliba> On Thu, Dec 11, 2014 at 4:03 PM, M S Vishwanath Bhat <[email protected]> wrote: > Hi, > > Can we have our own custom service with the zero deploy? If yes, how? > Google didn't show any satisfactory answers. > > Thanks in advance > > Best Regards, > Vishwanath > > -- > > --- > 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. > -- --- 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.
