Hi, I'm trying to develop an application that replicates remote objects locally and keeps them updated. This effectively boils down to a publication-subscription model where the local proxy object sends an interface (capability in capnp speak?) to the server that can be used to send it notifications. The server stores this interface pointer and responds with an "okay", then later uses the interface to send the local object notifications if the server-side object changes. It doesn't work however. If I use the interface pointer after the original "subscription" call has resolved, the message is never received on the client. If I use the interface _during_ the subscription request the message is received by the client, but the "then(...)" block on the server is not executed. I've looked through the calculator example, but that uses the client-side interface immediately.
- Can the interface pointers (capabilities right?) given in one call be stored for later use? I assume this must be the case but I can't be doing it correctly. - I'm using the ez-rpc interfaces. Is this one of the use cases not supported by them? - As this is my most basic test case, both the client and server are in the same compilation unit. I don't do any thread manipulation myself so I assume they're on the same event loop. Is this an issue? If so, I want the single process use case for testing, so is starting one or the other on a different thread sufficient? I can reduce the code to a simple example, but before going to the effort I wanted to make sure I'm not misunderstanding something. Thanks, Mark. Cap'n Proto version 0.5.3 -- 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.
