1. 03 May, 2017 1 commit
    • Ian Denhardt's avatar
      Remove references to obsolete isCallersFault · a901d43e
      Ian Denhardt authored
      At some point isCallersFault was marked as obsolete, but the description
      of abort still referenced it, suggesting particular usage. This patch
      removes said references.
      
      Since `git-diff` does *such* a good job with prose: This just removes
      the two parentheticals and re-flows the paragraph.
      a901d43e
  2. 07 Jan, 2016 1 commit
  3. 18 Nov, 2015 1 commit
  4. 29 Dec, 2014 1 commit
  5. 10 Dec, 2014 2 commits
  6. 08 Dec, 2014 1 commit
  7. 29 Nov, 2014 1 commit
    • Kenton Varda's avatar
      Simplify exceptions. Eliminate Durability. Rename Nature to Type and simplify it. · 4ee25e43
      Kenton Varda authored
      Distinguishing between "local bugs" and "preconditions" was proving difficult in practice, because a precondition failure in one function may very well indicate a bug in a calling function, but the exception may be thrown through that function, thus when caught the classification is nonsensical. The distinction also was not as useful as imagined. So, I eliminated this distinction.
      4ee25e43
  8. 06 Nov, 2014 1 commit
  9. 04 Nov, 2014 1 commit
  10. 19 Aug, 2014 1 commit
    • Kenton Varda's avatar
      Fix two subtle bugs with embargos, and improve docs. · 1cdcc24b
      Kenton Varda authored
      Bug 1
      -----
      
      If a Resolve message indicated that the promise had been rejected, the code would see the error cap as a local cap and erroneously believe that the promise had resolved back to a local capability, thereby requiring a Disembargo to be sent. The peer, on receiving the nonsensical Disembargo, would throw an exception and close the connection.
      
      The error message seen was: "expected target->getBrand() == this; 'Disembargo' of type 'senderLoopback' sent to an object that does not point back to the sender."
      
      Bug 2
      -----
      
      Disembargos are sent not only in response to Resolves, but also Returns, since capabilities in a returned message were previously accessible as PromisedAnswers. This means that we must apply the same rule that states that once a promise has been resolved, the promise must from then on forward all messages it receives strictly to the object to which it resolved, even if that object is itself a promise which later resolves to somewhere else. The code which sends Resolve messages was doing this correctly, but the code sending Return messages was not. They now both operate correctly. I've also added more explanation to the documentation in rpc.capnp.
      
      The error message seen was: "expected redirect == nullptr; 'Disembargo' of type 'senderLoopback' sent to an object that does not appear to have been the object of a previous 'Resolve' message."
      1cdcc24b
  11. 20 Jun, 2014 1 commit
    • Kenton Varda's avatar
      Change license to MIT. · 889204fe
      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
      889204fe
  12. 29 May, 2014 1 commit
  13. 05 May, 2014 1 commit
  14. 22 Jan, 2014 2 commits
  15. 10 Dec, 2013 1 commit
  16. 06 Dec, 2013 1 commit
  17. 05 Dec, 2013 2 commits
  18. 25 Nov, 2013 1 commit
  19. 23 Nov, 2013 1 commit
  20. 22 Nov, 2013 2 commits
  21. 21 Nov, 2013 1 commit
  22. 19 Nov, 2013 1 commit
  23. 18 Nov, 2013 2 commits
  24. 14 Nov, 2013 1 commit
  25. 12 Nov, 2013 1 commit
  26. 08 Nov, 2013 1 commit
  27. 23 Oct, 2013 1 commit
  28. 22 Oct, 2013 1 commit
  29. 17 Oct, 2013 1 commit
  30. 29 Sep, 2013 1 commit
  31. 26 Sep, 2013 1 commit
  32. 25 Sep, 2013 1 commit
  33. 19 Sep, 2013 2 commits
  34. 18 Sep, 2013 1 commit