- 18 Nov, 2016 1 commit
-
-
Kenton Varda authored
-
- 04 Sep, 2015 1 commit
-
-
Kenton Varda authored
-
- 30 Aug, 2015 1 commit
-
-
Christopher Jack Turner authored
Added capnp::TwoPartyServer::accept(...) this method allows capnp::TwoPartyServer to service arbitrary kj::AsyncIOStream objects such as those representing two-way pipes (socketpairs).
-
- 08 Jul, 2015 1 commit
-
-
Kenton Varda authored
-
- 03 Jul, 2015 1 commit
-
-
Kenton Varda authored
**The problem** The methods MessageReader::initCapTable() and MessageBuilder::getCapTable() always felt rather hacky. initCapTable() in particular feels like something that should be handled by the constructor. However, in practice, the cap table is often initialized based on a table encoded within the message itself. That is, an RPC message contains a "payload" which includes both the application-level message structure and a table of capabilities. The cap table has to be processed first, then initCapTable() is called on the overall message, before the application structure can safely be read. The really weird part about this is that even though the cap table only applies to one branch of the message (the payload), it is set on the *whole* MessageReader. This implies, for example, that it would be impossible to have a message that contains multiple payloads. We haven't had any need for such a thing, but an implemnetation that has such artificial limitations feels very wrong. MessageBuilder has similar issues going in the opposite direction. All of this ugliness potentially gets worse when we introduce "membranes". We want a way to intercept capabilities as they are being read from or written to an RPC payload. Currently, the only plausible way to do that is, again, to apply a transformation to all capabilities in the message. In practice it seems like this would work out OK, but it again feels wrong -- we really want to take a single Reader or Builder and "wrap" it so that transformations are applied on capabilities read/written through it. **The solution** This change fixes the problem by adding a new pointer to each struct/list Reader/Builder that tracks the current cap table. So, now a Reader or Builder for a particular sub-object can be "imbued" with a cap table without affecting any other existing Readers/Builders pointing into the same message. The cap table is inherited by child Readers/Builders obtained through the original one. This approach matches up nicely with membranes, which should make their implementation nice and clean. This change unfortunately means that Readers and Builders are now bigger, possibly with some performance impact.
-
- 06 May, 2015 1 commit
-
-
Kenton Varda authored
Add ability to construct a new bootstrap capability for each connecting client based on their authenticated VatId.
-
- 04 May, 2015 1 commit
-
-
Jason Paryani authored
-
- 15 Apr, 2015 1 commit
-
-
Kenton Varda authored
Add simple convenience classes for using TwoPartyVatNetwork as client or server, since I find myself rewriting this code over and over.
-
- 10 Dec, 2014 1 commit
-
-
Kenton Varda authored
-
- 04 Nov, 2014 1 commit
-
-
Kenton Varda authored
The 'objectId' field is now deprecated. Long-term, each vat will export no more than one "bootstrap interface" which can be obtained via 'Bootstrap'. Restoring SturdyRefs will be accomplished through higher-level interfaces specific to the VatNetwork in use. See comments for 'Bootstrap' in rpc.capnp for more discussion.
-
- 11 Sep, 2014 1 commit
-
-
Kenton Varda authored
Fix obscure bug where the last outgoing message (and any capabilities therein) would not get released (until a new message was sent, replacing it as the last). This took hours to track down, because it initially looked like "Release" messages weren't being honored in some cases (when they happened to be releasing a capability from the last message, and no subsequent messages were sent). Initial attempts to capture this in a unit test failed because the test of course used a subsequent call to detect if the capability had been released, which succeeded.
-
- 20 Jun, 2014 1 commit
-
-
Kenton Varda authored
For portions currently copyright by Kenton (most of it), transfer copyright to Sandstorm Development Group, Inc. (Kenton's company). The license change is practically meaningless, as MIT and BSD 2-clause are legally equivalent. However, the BSD 2-clause license is sometimes confused for its ugly siblings, BSD 3-clause and BSD 4-clause. The MIT license is more immediately recognizeable for what it is. Rémy Blank and Jason Choy (the two non-trivial contributors) are on record as approving this change: https://groups.google.com/d/msg/capnproto/xXDd2HUOCcc/gbe_COIuXKYJ
-
- 11 Feb, 2014 1 commit
-
-
Kenton Varda authored
Cleaner disconnect handling. Better fix for issue #71, and also simplifies the interface and improves robustness.
-
- 10 Feb, 2014 1 commit
-
-
Kenton Varda authored
Make TwoPartyVatNetwork::onDrained() work correctly on the server side. Previously only worked on the client side, where it's actually not very useful. Fixes #71. There's a deeper problem, though, that simply holding a capability received from the client will hold the dead connection open.
-
- 11 Dec, 2013 1 commit
-
-
Kenton Varda authored
Eliminate the concept of imbuing messages in favor of the simpler concept of setting a cap table directly on MessageReader / getting one from MessageBuilder. This eliminates capability-context entirely. This was made possible by the earlier change which moved capabilities to a separate table rather than storing CapDescriptors inline, but I didn't realize it at the time.
-
- 05 Dec, 2013 2 commits
-
-
Kenton Varda authored
-
Kenton Varda authored
Make all Promise methods consistently consume the promise (returning a new promise when it makes sense), rename daemonize -> detach, and make eagerlyEvaluate() require an error handler (this caught several places where I forgot to use one).
-
- 29 Nov, 2013 1 commit
-
-
Kenton Varda authored
-
- 28 Nov, 2013 1 commit
-
-
Kenton Varda authored
Revamp concurrency model, part 1: EventLoop no longer allows cross-thread event queuing, simplifying many things. Capability clients are no longer thread-safe, so they don't have to be so const. In the future, explicit ways to communicate between threads will be re-added, but threads will be treated more like separate vats that just happen to have a particularly fat pipe. Upcoming: Remove mutexes.
-
- 21 Nov, 2013 1 commit
-
-
Kenton Varda authored
-
- 18 Nov, 2013 1 commit
-
-
Kenton Varda authored
-
- 08 Nov, 2013 2 commits
-
-
Kenton Varda authored
-
Kenton Varda authored
Implement two-party network. The first RPC call over a socket took place at 2013-11-08 14:46:43 -0800 and completed successfully.
-