- 11 Jan, 2018 1 commit
-
-
Kenton Varda authored
@kloepper pointed out a while back that every compiler you've ever heard of supports this. Plus, it's more concise, it's not prone to copy-paste errors, and it looks nicer. At the time I wanted to remain consistent and I didn't feel like spending the time to update all my existing code. But, every time I've added a new header since I've cursed the include guard, so I finally broke down and changed it.
-
- 02 Apr, 2016 1 commit
-
-
Liam Staskawicz authored
fixes #304
-
- 07 Jan, 2016 1 commit
-
-
David Renshaw authored
-
- 14 Sep, 2015 1 commit
-
-
Kamal Marhubi 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
-
- 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 2 commits
-
-
Kenton Varda authored
-
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
-
- 22 Nov, 2014 1 commit
-
-
Kenton Varda authored
This prevents the compiler from reporting warnings in these headers while compiling application code. Hopefully this will stem the never-ending stream of complaints from people who enable pedantic warnings.
-
- 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.
-
- 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.
-
- 04 Dec, 2013 1 commit
-
-
Kenton Varda authored
-
- 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.
-
- 18 Nov, 2013 1 commit
-
-
Kenton Varda authored
-
- 14 Nov, 2013 1 commit
-
-
Kenton Varda authored
In RPC protocol, rename request -> params, answer -> results. Also fix up Join stuff in rpc-twoparty.capnp, because it was sort of wrong.
-
- 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.
-