I'm not sure about b), but a) is a known issue: #363 <https://github.com/sandstorm-io/capnproto/issues/363>
On Fri, Dec 16, 2016 at 6:36 AM Andreas Stenius <[email protected]> wrote: > Hi, > > Been working with pycapnp a while now. And when it works, it is really > nice, but when I make a mistake, it can be a bit hard to track down what > went wrong (the stack traces on the form of hex addresses doesn't help me > much, or I just don't know which tools to apply on them). > > I have two questions, > > a) Consider the following schema snippet: > > interface Foo { > meth @0 (a :Text, b :Bar) -> (); > } > > interface Bar { > } > > Is there any way to make the b parameter optional, or accept None as input > when invoking it, on the python side? > > b) Using RPC, is there any way on the server side to detect when a client > disconnects? > Now I find myself relying on __del__ being called on server interfaces > I've created and sent to the client (but that only works if I refer from > holding a reference to it myself, and weak refs doesn't seem to work on > these little buggers) ;) > > And if yes, how to identify the client in question. > > > Thanks. > > -- > You received this message because you are subscribed to the Google Groups > "Cap'n Proto" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > Visit this group at https://groups.google.com/group/capnproto. > -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/capnproto.
