Quoting Ryan Patterson (2020-09-16 00:44:05) > That said, I'm not convinced about your store use case. It doesn't > seem like something that needs to be integral to the capnp protocol, > since there's already a shared schema between the peers.
Having slept on it I think you're right; the data store can probably be dealt with in a way that is orthogonal to Introspectable. > I've dropped the second interface since, as far as I can tell, the > only place this needs to be implemented is again on the root object > from Bootstrap/Accept. I've kept the List(UInt64), but switched to > a multi-get for the schema fetcher, > which has the nice advantage of allowing pipelining if you believe > ahead of time you won't have the schema for the returned interfaces. I don't think this currently works; afaik there's no way to feed a pending non-capability pointer directly as the argument to another call; it only works on capabilities. A possible alternative would be to have a method that just explicitly requests the schema for all of the interfaces the receiver supports. -Ian -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/capnproto/160027549952.2006.11681367044296526532%40localhost.localdomain.
