annotate win64-msvc/include/capnp/rpc.h @ 148:b4bfdf10c4b3

Update Win64 capnp builds to v0.6
author Chris Cannam <cannam@all-day-breakfast.com>
date Mon, 22 May 2017 18:56:49 +0100
parents 42a73082be24
children
rev   line source
cannam@148 1 // Copyright (c) 2013-2014 Sandstorm Development Group, Inc. and contributors
cannam@148 2 // Licensed under the MIT License:
cannam@148 3 //
cannam@148 4 // Permission is hereby granted, free of charge, to any person obtaining a copy
cannam@148 5 // of this software and associated documentation files (the "Software"), to deal
cannam@148 6 // in the Software without restriction, including without limitation the rights
cannam@148 7 // to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
cannam@148 8 // copies of the Software, and to permit persons to whom the Software is
cannam@148 9 // furnished to do so, subject to the following conditions:
cannam@148 10 //
cannam@148 11 // The above copyright notice and this permission notice shall be included in
cannam@148 12 // all copies or substantial portions of the Software.
cannam@148 13 //
cannam@148 14 // THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
cannam@148 15 // IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
cannam@148 16 // FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
cannam@148 17 // AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
cannam@148 18 // LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
cannam@148 19 // OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
cannam@148 20 // THE SOFTWARE.
cannam@148 21
cannam@148 22 #ifndef CAPNP_RPC_H_
cannam@148 23 #define CAPNP_RPC_H_
cannam@148 24
cannam@148 25 #if defined(__GNUC__) && !defined(CAPNP_HEADER_WARNINGS)
cannam@148 26 #pragma GCC system_header
cannam@148 27 #endif
cannam@148 28
cannam@148 29 #include "capability.h"
cannam@148 30 #include "rpc-prelude.h"
cannam@148 31
cannam@148 32 namespace capnp {
cannam@148 33
cannam@148 34 template <typename VatId, typename ProvisionId, typename RecipientId,
cannam@148 35 typename ThirdPartyCapId, typename JoinResult>
cannam@148 36 class VatNetwork;
cannam@148 37 template <typename SturdyRefObjectId>
cannam@148 38 class SturdyRefRestorer;
cannam@148 39
cannam@148 40 template <typename VatId>
cannam@148 41 class BootstrapFactory: public _::BootstrapFactoryBase {
cannam@148 42 // Interface that constructs per-client bootstrap interfaces. Use this if you want each client
cannam@148 43 // who connects to see a different bootstrap interface based on their (authenticated) VatId.
cannam@148 44 // This allows an application to bootstrap off of the authentication performed at the VatNetwork
cannam@148 45 // level. (Typically VatId is some sort of public key.)
cannam@148 46 //
cannam@148 47 // This is only useful for multi-party networks. For TwoPartyVatNetwork, there's no reason to
cannam@148 48 // use a BootstrapFactory; just specify a single bootstrap capability in this case.
cannam@148 49
cannam@148 50 public:
cannam@148 51 virtual Capability::Client createFor(typename VatId::Reader clientId) = 0;
cannam@148 52 // Create a bootstrap capability appropriate for exposing to the given client. VatNetwork will
cannam@148 53 // have authenticated the client VatId before this is called.
cannam@148 54
cannam@148 55 private:
cannam@148 56 Capability::Client baseCreateFor(AnyStruct::Reader clientId) override;
cannam@148 57 };
cannam@148 58
cannam@148 59 template <typename VatId>
cannam@148 60 class RpcSystem: public _::RpcSystemBase {
cannam@148 61 // Represents the RPC system, which is the portal to objects available on the network.
cannam@148 62 //
cannam@148 63 // The RPC implementation sits on top of an implementation of `VatNetwork`. The `VatNetwork`
cannam@148 64 // determines how to form connections between vats -- specifically, two-way, private, reliable,
cannam@148 65 // sequenced datagram connections. The RPC implementation determines how to use such connections
cannam@148 66 // to manage object references and make method calls.
cannam@148 67 //
cannam@148 68 // See `makeRpcServer()` and `makeRpcClient()` below for convenient syntax for setting up an
cannam@148 69 // `RpcSystem` given a `VatNetwork`.
cannam@148 70 //
cannam@148 71 // See `ez-rpc.h` for an even simpler interface for setting up RPC in a typical two-party
cannam@148 72 // client/server scenario.
cannam@148 73
cannam@148 74 public:
cannam@148 75 template <typename ProvisionId, typename RecipientId,
cannam@148 76 typename ThirdPartyCapId, typename JoinResult>
cannam@148 77 RpcSystem(
cannam@148 78 VatNetwork<VatId, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>& network,
cannam@148 79 kj::Maybe<Capability::Client> bootstrapInterface,
cannam@148 80 kj::Maybe<RealmGateway<>::Client> gateway = nullptr);
cannam@148 81
cannam@148 82 template <typename ProvisionId, typename RecipientId,
cannam@148 83 typename ThirdPartyCapId, typename JoinResult>
cannam@148 84 RpcSystem(
cannam@148 85 VatNetwork<VatId, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>& network,
cannam@148 86 BootstrapFactory<VatId>& bootstrapFactory,
cannam@148 87 kj::Maybe<RealmGateway<>::Client> gateway = nullptr);
cannam@148 88
cannam@148 89 template <typename ProvisionId, typename RecipientId,
cannam@148 90 typename ThirdPartyCapId, typename JoinResult,
cannam@148 91 typename LocalSturdyRefObjectId>
cannam@148 92 RpcSystem(
cannam@148 93 VatNetwork<VatId, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>& network,
cannam@148 94 SturdyRefRestorer<LocalSturdyRefObjectId>& restorer);
cannam@148 95
cannam@148 96 RpcSystem(RpcSystem&& other) = default;
cannam@148 97
cannam@148 98 Capability::Client bootstrap(typename VatId::Reader vatId);
cannam@148 99 // Connect to the given vat and return its bootstrap interface.
cannam@148 100
cannam@148 101 Capability::Client restore(typename VatId::Reader hostId, AnyPointer::Reader objectId)
cannam@148 102 KJ_DEPRECATED("Please transition to using a bootstrap interface instead.");
cannam@148 103 // ** DEPRECATED **
cannam@148 104 //
cannam@148 105 // Restores the given SturdyRef from the network and return the capability representing it.
cannam@148 106 //
cannam@148 107 // `hostId` identifies the host from which to request the ref, in the format specified by the
cannam@148 108 // `VatNetwork` in use. `objectId` is the object ID in whatever format is expected by said host.
cannam@148 109 //
cannam@148 110 // This method will be removed in a future version of Cap'n Proto. Instead, please transition
cannam@148 111 // to using bootstrap(), which is equivalent to calling restore() with a null `objectId`.
cannam@148 112 // You may emulate the old concept of object IDs by exporting a bootstrap interface which has
cannam@148 113 // methods that can be used to obtain other capabilities by ID.
cannam@148 114
cannam@148 115 void setFlowLimit(size_t words);
cannam@148 116 // Sets the incoming call flow limit. If more than `words` worth of call messages have not yet
cannam@148 117 // received responses, the RpcSystem will not read further messages from the stream. This can be
cannam@148 118 // used as a crude way to prevent a resource exhaustion attack (or bug) in which a peer makes an
cannam@148 119 // excessive number of simultaneous calls that consume the receiver's RAM.
cannam@148 120 //
cannam@148 121 // There are some caveats. When over the flow limit, all messages are blocked, including returns.
cannam@148 122 // If the outstanding calls are themselves waiting on calls going in the opposite direction, the
cannam@148 123 // flow limit may prevent those calls from completing, leading to deadlock. However, a
cannam@148 124 // sufficiently high limit should make this unlikely.
cannam@148 125 //
cannam@148 126 // Note that a call's parameter size counts against the flow limit until the call returns, even
cannam@148 127 // if the recipient calls releaseParams() to free the parameter memory early. This is because
cannam@148 128 // releaseParams() may simply indicate that the parameters have been forwarded to another
cannam@148 129 // machine, but are still in-memory there. For illustration, say that Alice made a call to Bob
cannam@148 130 // who forwarded the call to Carol. Bob has imposed a flow limit on Alice. Alice's calls are
cannam@148 131 // being forwarded to Carol, so Bob never keeps the parameters in-memory for more than a brief
cannam@148 132 // period. However, the flow limit counts all calls that haven't returned, even if Bob has
cannam@148 133 // already freed the memory they consumed. You might argue that the right solution here is
cannam@148 134 // instead for Carol to impose her own flow limit on Bob. This has a serious problem, though:
cannam@148 135 // Bob might be forwarding requests to Carol on behalf of many different parties, not just Alice.
cannam@148 136 // If Alice can pump enough data to hit the Bob -> Carol flow limit, then those other parties
cannam@148 137 // will be disrupted. Thus, we can only really impose the limit on the Alice -> Bob link, which
cannam@148 138 // only affects Alice. We need that one flow limit to limit Alice's impact on the whole system,
cannam@148 139 // so it has to count all in-flight calls.
cannam@148 140 //
cannam@148 141 // In Sandstorm, flow limits are imposed by the supervisor on calls coming out of a grain, in
cannam@148 142 // order to prevent a grain from inundating the system with in-flight calls. In practice, the
cannam@148 143 // main time this happens is when a grain is pushing a large file download and doesn't implement
cannam@148 144 // proper cooperative flow control.
cannam@148 145 };
cannam@148 146
cannam@148 147 template <typename VatId, typename ProvisionId, typename RecipientId,
cannam@148 148 typename ThirdPartyCapId, typename JoinResult>
cannam@148 149 RpcSystem<VatId> makeRpcServer(
cannam@148 150 VatNetwork<VatId, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>& network,
cannam@148 151 Capability::Client bootstrapInterface);
cannam@148 152 // Make an RPC server. Typical usage (e.g. in a main() function):
cannam@148 153 //
cannam@148 154 // MyEventLoop eventLoop;
cannam@148 155 // kj::WaitScope waitScope(eventLoop);
cannam@148 156 // MyNetwork network;
cannam@148 157 // MyMainInterface::Client bootstrap = makeMain();
cannam@148 158 // auto server = makeRpcServer(network, bootstrap);
cannam@148 159 // kj::NEVER_DONE.wait(waitScope); // run forever
cannam@148 160 //
cannam@148 161 // See also ez-rpc.h, which has simpler instructions for the common case of a two-party
cannam@148 162 // client-server RPC connection.
cannam@148 163
cannam@148 164 template <typename VatId, typename ProvisionId, typename RecipientId,
cannam@148 165 typename ThirdPartyCapId, typename JoinResult, typename RealmGatewayClient,
cannam@148 166 typename InternalRef = _::InternalRefFromRealmGatewayClient<RealmGatewayClient>,
cannam@148 167 typename ExternalRef = _::ExternalRefFromRealmGatewayClient<RealmGatewayClient>>
cannam@148 168 RpcSystem<VatId> makeRpcServer(
cannam@148 169 VatNetwork<VatId, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>& network,
cannam@148 170 Capability::Client bootstrapInterface, RealmGatewayClient gateway);
cannam@148 171 // Make an RPC server for a VatNetwork that resides in a different realm from the application.
cannam@148 172 // The given RealmGateway is used to translate SturdyRefs between the app's ("internal") format
cannam@148 173 // and the network's ("external") format.
cannam@148 174
cannam@148 175 template <typename VatId, typename ProvisionId, typename RecipientId,
cannam@148 176 typename ThirdPartyCapId, typename JoinResult>
cannam@148 177 RpcSystem<VatId> makeRpcServer(
cannam@148 178 VatNetwork<VatId, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>& network,
cannam@148 179 BootstrapFactory<VatId>& bootstrapFactory);
cannam@148 180 // Make an RPC server that can serve different bootstrap interfaces to different clients via a
cannam@148 181 // BootstrapInterface.
cannam@148 182
cannam@148 183 template <typename VatId, typename ProvisionId, typename RecipientId,
cannam@148 184 typename ThirdPartyCapId, typename JoinResult, typename RealmGatewayClient,
cannam@148 185 typename InternalRef = _::InternalRefFromRealmGatewayClient<RealmGatewayClient>,
cannam@148 186 typename ExternalRef = _::ExternalRefFromRealmGatewayClient<RealmGatewayClient>>
cannam@148 187 RpcSystem<VatId> makeRpcServer(
cannam@148 188 VatNetwork<VatId, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>& network,
cannam@148 189 BootstrapFactory<VatId>& bootstrapFactory, RealmGatewayClient gateway);
cannam@148 190 // Make an RPC server that can serve different bootstrap interfaces to different clients via a
cannam@148 191 // BootstrapInterface and communicates with a different realm than the application is in via a
cannam@148 192 // RealmGateway.
cannam@148 193
cannam@148 194 template <typename VatId, typename LocalSturdyRefObjectId,
cannam@148 195 typename ProvisionId, typename RecipientId, typename ThirdPartyCapId, typename JoinResult>
cannam@148 196 RpcSystem<VatId> makeRpcServer(
cannam@148 197 VatNetwork<VatId, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>& network,
cannam@148 198 SturdyRefRestorer<LocalSturdyRefObjectId>& restorer)
cannam@148 199 KJ_DEPRECATED("Please transition to using a bootstrap interface instead.");
cannam@148 200 // ** DEPRECATED **
cannam@148 201 //
cannam@148 202 // Create an RPC server which exports multiple main interfaces by object ID. The `restorer` object
cannam@148 203 // can be used to look up objects by ID.
cannam@148 204 //
cannam@148 205 // Please transition to exporting only one interface, which is known as the "bootstrap" interface.
cannam@148 206 // For backwards-compatibility with old clients, continue to implement SturdyRefRestorer, but
cannam@148 207 // return the new bootstrap interface when the request object ID is null. When new clients connect
cannam@148 208 // and request the bootstrap interface, they will get that interface. Eventually, once all clients
cannam@148 209 // are updated to request only the bootstrap interface, stop implementing SturdyRefRestorer and
cannam@148 210 // switch to passing the bootstrap capability itself as the second parameter to `makeRpcServer()`.
cannam@148 211
cannam@148 212 template <typename VatId, typename ProvisionId,
cannam@148 213 typename RecipientId, typename ThirdPartyCapId, typename JoinResult>
cannam@148 214 RpcSystem<VatId> makeRpcClient(
cannam@148 215 VatNetwork<VatId, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>& network);
cannam@148 216 // Make an RPC client. Typical usage (e.g. in a main() function):
cannam@148 217 //
cannam@148 218 // MyEventLoop eventLoop;
cannam@148 219 // kj::WaitScope waitScope(eventLoop);
cannam@148 220 // MyNetwork network;
cannam@148 221 // auto client = makeRpcClient(network);
cannam@148 222 // MyCapability::Client cap = client.restore(hostId, objId).castAs<MyCapability>();
cannam@148 223 // auto response = cap.fooRequest().send().wait(waitScope);
cannam@148 224 // handleMyResponse(response);
cannam@148 225 //
cannam@148 226 // See also ez-rpc.h, which has simpler instructions for the common case of a two-party
cannam@148 227 // client-server RPC connection.
cannam@148 228
cannam@148 229 template <typename VatId, typename ProvisionId, typename RecipientId,
cannam@148 230 typename ThirdPartyCapId, typename JoinResult, typename RealmGatewayClient,
cannam@148 231 typename InternalRef = _::InternalRefFromRealmGatewayClient<RealmGatewayClient>,
cannam@148 232 typename ExternalRef = _::ExternalRefFromRealmGatewayClient<RealmGatewayClient>>
cannam@148 233 RpcSystem<VatId> makeRpcClient(
cannam@148 234 VatNetwork<VatId, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>& network,
cannam@148 235 RealmGatewayClient gateway);
cannam@148 236 // Make an RPC client for a VatNetwork that resides in a different realm from the application.
cannam@148 237 // The given RealmGateway is used to translate SturdyRefs between the app's ("internal") format
cannam@148 238 // and the network's ("external") format.
cannam@148 239
cannam@148 240 template <typename SturdyRefObjectId>
cannam@148 241 class SturdyRefRestorer: public _::SturdyRefRestorerBase {
cannam@148 242 // ** DEPRECATED **
cannam@148 243 //
cannam@148 244 // In Cap'n Proto 0.4.x, applications could export multiple main interfaces identified by
cannam@148 245 // object IDs. The callback used to map object IDs to objects was `SturdyRefRestorer`, as we
cannam@148 246 // imagined this would eventually be used for restoring SturdyRefs as well. In practice, it was
cannam@148 247 // never used for real SturdyRefs, only for exporting singleton objects under well-known names.
cannam@148 248 //
cannam@148 249 // The new preferred strategy is to export only a _single_ such interface, called the
cannam@148 250 // "bootstrap interface". That interface can itself have methods for obtaining other objects, of
cannam@148 251 // course, but that is up to the app. `SturdyRefRestorer` exists for backwards-compatibility.
cannam@148 252 //
cannam@148 253 // Hint: Use SturdyRefRestorer<capnp::Text> to define a server that exports services under
cannam@148 254 // string names.
cannam@148 255
cannam@148 256 public:
cannam@148 257 virtual Capability::Client restore(typename SturdyRefObjectId::Reader ref)
cannam@148 258 KJ_DEPRECATED(
cannam@148 259 "Please transition to using bootstrap interfaces instead of SturdyRefRestorer.") = 0;
cannam@148 260 // Restore the given object, returning a capability representing it.
cannam@148 261
cannam@148 262 private:
cannam@148 263 Capability::Client baseRestore(AnyPointer::Reader ref) override final;
cannam@148 264 };
cannam@148 265
cannam@148 266 // =======================================================================================
cannam@148 267 // VatNetwork
cannam@148 268
cannam@148 269 class OutgoingRpcMessage {
cannam@148 270 // A message to be sent by a `VatNetwork`.
cannam@148 271
cannam@148 272 public:
cannam@148 273 virtual AnyPointer::Builder getBody() = 0;
cannam@148 274 // Get the message body, which the caller may fill in any way it wants. (The standard RPC
cannam@148 275 // implementation initializes it as a Message as defined in rpc.capnp.)
cannam@148 276
cannam@148 277 virtual void send() = 0;
cannam@148 278 // Send the message, or at least put it in a queue to be sent later. Note that the builder
cannam@148 279 // returned by `getBody()` remains valid at least until the `OutgoingRpcMessage` is destroyed.
cannam@148 280 };
cannam@148 281
cannam@148 282 class IncomingRpcMessage {
cannam@148 283 // A message received from a `VatNetwork`.
cannam@148 284
cannam@148 285 public:
cannam@148 286 virtual AnyPointer::Reader getBody() = 0;
cannam@148 287 // Get the message body, to be interpreted by the caller. (The standard RPC implementation
cannam@148 288 // interprets it as a Message as defined in rpc.capnp.)
cannam@148 289 };
cannam@148 290
cannam@148 291 template <typename VatId, typename ProvisionId, typename RecipientId,
cannam@148 292 typename ThirdPartyCapId, typename JoinResult>
cannam@148 293 class VatNetwork: public _::VatNetworkBase {
cannam@148 294 // Cap'n Proto RPC operates between vats, where a "vat" is some sort of host of objects.
cannam@148 295 // Typically one Cap'n Proto process (in the Unix sense) is one vat. The RPC system is what
cannam@148 296 // allows calls between objects hosted in different vats.
cannam@148 297 //
cannam@148 298 // The RPC implementation sits on top of an implementation of `VatNetwork`. The `VatNetwork`
cannam@148 299 // determines how to form connections between vats -- specifically, two-way, private, reliable,
cannam@148 300 // sequenced datagram connections. The RPC implementation determines how to use such connections
cannam@148 301 // to manage object references and make method calls.
cannam@148 302 //
cannam@148 303 // The most common implementation of VatNetwork is TwoPartyVatNetwork (rpc-twoparty.h). Most
cannam@148 304 // simple client-server apps will want to use it. (You may even want to use the EZ RPC
cannam@148 305 // interfaces in `ez-rpc.h` and avoid all of this.)
cannam@148 306 //
cannam@148 307 // TODO(someday): Provide a standard implementation for the public internet.
cannam@148 308
cannam@148 309 public:
cannam@148 310 class Connection;
cannam@148 311
cannam@148 312 struct ConnectionAndProvisionId {
cannam@148 313 // Result of connecting to a vat introduced by another vat.
cannam@148 314
cannam@148 315 kj::Own<Connection> connection;
cannam@148 316 // Connection to the new vat.
cannam@148 317
cannam@148 318 kj::Own<OutgoingRpcMessage> firstMessage;
cannam@148 319 // An already-allocated `OutgoingRpcMessage` associated with `connection`. The RPC system will
cannam@148 320 // construct this as an `Accept` message and send it.
cannam@148 321
cannam@148 322 Orphan<ProvisionId> provisionId;
cannam@148 323 // A `ProvisionId` already allocated inside `firstMessage`, which the RPC system will use to
cannam@148 324 // build the `Accept` message.
cannam@148 325 };
cannam@148 326
cannam@148 327 class Connection: public _::VatNetworkBase::Connection {
cannam@148 328 // A two-way RPC connection.
cannam@148 329 //
cannam@148 330 // This object may represent a connection that doesn't exist yet, but is expected to exist
cannam@148 331 // in the future. In this case, sent messages will automatically be queued and sent once the
cannam@148 332 // connection is ready, so that the caller doesn't need to know the difference.
cannam@148 333
cannam@148 334 public:
cannam@148 335 // Level 0 features ----------------------------------------------
cannam@148 336
cannam@148 337 virtual typename VatId::Reader getPeerVatId() = 0;
cannam@148 338 // Returns the connected vat's authenticated VatId. It is the VatNetwork's responsibility to
cannam@148 339 // authenticate this, so that the caller can be assured that they are really talking to the
cannam@148 340 // identified vat and not an imposter.
cannam@148 341
cannam@148 342 virtual kj::Own<OutgoingRpcMessage> newOutgoingMessage(uint firstSegmentWordSize) override = 0;
cannam@148 343 // Allocate a new message to be sent on this connection.
cannam@148 344 //
cannam@148 345 // If `firstSegmentWordSize` is non-zero, it should be treated as a hint suggesting how large
cannam@148 346 // to make the first segment. This is entirely a hint and the connection may adjust it up or
cannam@148 347 // down. If it is zero, the connection should choose the size itself.
cannam@148 348
cannam@148 349 virtual kj::Promise<kj::Maybe<kj::Own<IncomingRpcMessage>>> receiveIncomingMessage() override = 0;
cannam@148 350 // Wait for a message to be received and return it. If the read stream cleanly terminates,
cannam@148 351 // return null. If any other problem occurs, throw an exception.
cannam@148 352
cannam@148 353 virtual kj::Promise<void> shutdown() override KJ_WARN_UNUSED_RESULT = 0;
cannam@148 354 // Waits until all outgoing messages have been sent, then shuts down the outgoing stream. The
cannam@148 355 // returned promise resolves after shutdown is complete.
cannam@148 356
cannam@148 357 private:
cannam@148 358 AnyStruct::Reader baseGetPeerVatId() override;
cannam@148 359 };
cannam@148 360
cannam@148 361 // Level 0 features ------------------------------------------------
cannam@148 362
cannam@148 363 virtual kj::Maybe<kj::Own<Connection>> connect(typename VatId::Reader hostId) = 0;
cannam@148 364 // Connect to a VatId. Note that this method immediately returns a `Connection`, even
cannam@148 365 // if the network connection has not yet been established. Messages can be queued to this
cannam@148 366 // connection and will be delivered once it is open. The caller must attempt to read from the
cannam@148 367 // connection to verify that it actually succeeded; the read will fail if the connection
cannam@148 368 // couldn't be opened. Some network implementations may actually start sending messages before
cannam@148 369 // hearing back from the server at all, to avoid a round trip.
cannam@148 370 //
cannam@148 371 // Returns nullptr if `hostId` refers to the local host.
cannam@148 372
cannam@148 373 virtual kj::Promise<kj::Own<Connection>> accept() = 0;
cannam@148 374 // Wait for the next incoming connection and return it.
cannam@148 375
cannam@148 376 // Level 4 features ------------------------------------------------
cannam@148 377 // TODO(someday)
cannam@148 378
cannam@148 379 private:
cannam@148 380 kj::Maybe<kj::Own<_::VatNetworkBase::Connection>>
cannam@148 381 baseConnect(AnyStruct::Reader hostId) override final;
cannam@148 382 kj::Promise<kj::Own<_::VatNetworkBase::Connection>> baseAccept() override final;
cannam@148 383 };
cannam@148 384
cannam@148 385 // =======================================================================================
cannam@148 386 // ***************************************************************************************
cannam@148 387 // Inline implementation details start here
cannam@148 388 // ***************************************************************************************
cannam@148 389 // =======================================================================================
cannam@148 390
cannam@148 391 template <typename VatId>
cannam@148 392 Capability::Client BootstrapFactory<VatId>::baseCreateFor(AnyStruct::Reader clientId) {
cannam@148 393 return createFor(clientId.as<VatId>());
cannam@148 394 }
cannam@148 395
cannam@148 396 template <typename SturdyRef, typename ProvisionId, typename RecipientId,
cannam@148 397 typename ThirdPartyCapId, typename JoinResult>
cannam@148 398 kj::Maybe<kj::Own<_::VatNetworkBase::Connection>>
cannam@148 399 VatNetwork<SturdyRef, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>::
cannam@148 400 baseConnect(AnyStruct::Reader ref) {
cannam@148 401 auto maybe = connect(ref.as<SturdyRef>());
cannam@148 402 return maybe.map([](kj::Own<Connection>& conn) -> kj::Own<_::VatNetworkBase::Connection> {
cannam@148 403 return kj::mv(conn);
cannam@148 404 });
cannam@148 405 }
cannam@148 406
cannam@148 407 template <typename SturdyRef, typename ProvisionId, typename RecipientId,
cannam@148 408 typename ThirdPartyCapId, typename JoinResult>
cannam@148 409 kj::Promise<kj::Own<_::VatNetworkBase::Connection>>
cannam@148 410 VatNetwork<SturdyRef, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>::baseAccept() {
cannam@148 411 return accept().then(
cannam@148 412 [](kj::Own<Connection>&& connection) -> kj::Own<_::VatNetworkBase::Connection> {
cannam@148 413 return kj::mv(connection);
cannam@148 414 });
cannam@148 415 }
cannam@148 416
cannam@148 417 template <typename SturdyRef, typename ProvisionId, typename RecipientId,
cannam@148 418 typename ThirdPartyCapId, typename JoinResult>
cannam@148 419 AnyStruct::Reader VatNetwork<
cannam@148 420 SturdyRef, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>::
cannam@148 421 Connection::baseGetPeerVatId() {
cannam@148 422 return getPeerVatId();
cannam@148 423 }
cannam@148 424
cannam@148 425 template <typename SturdyRef>
cannam@148 426 Capability::Client SturdyRefRestorer<SturdyRef>::baseRestore(AnyPointer::Reader ref) {
cannam@148 427 #pragma GCC diagnostic push
cannam@148 428 #pragma GCC diagnostic ignored "-Wdeprecated-declarations"
cannam@148 429 return restore(ref.getAs<SturdyRef>());
cannam@148 430 #pragma GCC diagnostic pop
cannam@148 431 }
cannam@148 432
cannam@148 433 template <typename VatId>
cannam@148 434 template <typename ProvisionId, typename RecipientId,
cannam@148 435 typename ThirdPartyCapId, typename JoinResult>
cannam@148 436 RpcSystem<VatId>::RpcSystem(
cannam@148 437 VatNetwork<VatId, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>& network,
cannam@148 438 kj::Maybe<Capability::Client> bootstrap,
cannam@148 439 kj::Maybe<RealmGateway<>::Client> gateway)
cannam@148 440 : _::RpcSystemBase(network, kj::mv(bootstrap), kj::mv(gateway)) {}
cannam@148 441
cannam@148 442 template <typename VatId>
cannam@148 443 template <typename ProvisionId, typename RecipientId,
cannam@148 444 typename ThirdPartyCapId, typename JoinResult>
cannam@148 445 RpcSystem<VatId>::RpcSystem(
cannam@148 446 VatNetwork<VatId, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>& network,
cannam@148 447 BootstrapFactory<VatId>& bootstrapFactory,
cannam@148 448 kj::Maybe<RealmGateway<>::Client> gateway)
cannam@148 449 : _::RpcSystemBase(network, bootstrapFactory, kj::mv(gateway)) {}
cannam@148 450
cannam@148 451 template <typename VatId>
cannam@148 452 template <typename ProvisionId, typename RecipientId,
cannam@148 453 typename ThirdPartyCapId, typename JoinResult,
cannam@148 454 typename LocalSturdyRefObjectId>
cannam@148 455 RpcSystem<VatId>::RpcSystem(
cannam@148 456 VatNetwork<VatId, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>& network,
cannam@148 457 SturdyRefRestorer<LocalSturdyRefObjectId>& restorer)
cannam@148 458 : _::RpcSystemBase(network, restorer) {}
cannam@148 459
cannam@148 460 template <typename VatId>
cannam@148 461 Capability::Client RpcSystem<VatId>::bootstrap(typename VatId::Reader vatId) {
cannam@148 462 return baseBootstrap(_::PointerHelpers<VatId>::getInternalReader(vatId));
cannam@148 463 }
cannam@148 464
cannam@148 465 template <typename VatId>
cannam@148 466 Capability::Client RpcSystem<VatId>::restore(
cannam@148 467 typename VatId::Reader hostId, AnyPointer::Reader objectId) {
cannam@148 468 return baseRestore(_::PointerHelpers<VatId>::getInternalReader(hostId), objectId);
cannam@148 469 }
cannam@148 470
cannam@148 471 template <typename VatId>
cannam@148 472 inline void RpcSystem<VatId>::setFlowLimit(size_t words) {
cannam@148 473 baseSetFlowLimit(words);
cannam@148 474 }
cannam@148 475
cannam@148 476 template <typename VatId, typename ProvisionId, typename RecipientId,
cannam@148 477 typename ThirdPartyCapId, typename JoinResult>
cannam@148 478 RpcSystem<VatId> makeRpcServer(
cannam@148 479 VatNetwork<VatId, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>& network,
cannam@148 480 Capability::Client bootstrapInterface) {
cannam@148 481 return RpcSystem<VatId>(network, kj::mv(bootstrapInterface));
cannam@148 482 }
cannam@148 483
cannam@148 484 template <typename VatId, typename ProvisionId, typename RecipientId,
cannam@148 485 typename ThirdPartyCapId, typename JoinResult,
cannam@148 486 typename RealmGatewayClient, typename InternalRef, typename ExternalRef>
cannam@148 487 RpcSystem<VatId> makeRpcServer(
cannam@148 488 VatNetwork<VatId, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>& network,
cannam@148 489 Capability::Client bootstrapInterface, RealmGatewayClient gateway) {
cannam@148 490 return RpcSystem<VatId>(network, kj::mv(bootstrapInterface),
cannam@148 491 gateway.template castAs<RealmGateway<>>());
cannam@148 492 }
cannam@148 493
cannam@148 494 template <typename VatId, typename ProvisionId, typename RecipientId,
cannam@148 495 typename ThirdPartyCapId, typename JoinResult>
cannam@148 496 RpcSystem<VatId> makeRpcServer(
cannam@148 497 VatNetwork<VatId, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>& network,
cannam@148 498 BootstrapFactory<VatId>& bootstrapFactory) {
cannam@148 499 return RpcSystem<VatId>(network, bootstrapFactory);
cannam@148 500 }
cannam@148 501
cannam@148 502 template <typename VatId, typename ProvisionId, typename RecipientId,
cannam@148 503 typename ThirdPartyCapId, typename JoinResult,
cannam@148 504 typename RealmGatewayClient, typename InternalRef, typename ExternalRef>
cannam@148 505 RpcSystem<VatId> makeRpcServer(
cannam@148 506 VatNetwork<VatId, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>& network,
cannam@148 507 BootstrapFactory<VatId>& bootstrapFactory, RealmGatewayClient gateway) {
cannam@148 508 return RpcSystem<VatId>(network, bootstrapFactory, gateway.template castAs<RealmGateway<>>());
cannam@148 509 }
cannam@148 510
cannam@148 511 template <typename VatId, typename LocalSturdyRefObjectId,
cannam@148 512 typename ProvisionId, typename RecipientId, typename ThirdPartyCapId, typename JoinResult>
cannam@148 513 RpcSystem<VatId> makeRpcServer(
cannam@148 514 VatNetwork<VatId, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>& network,
cannam@148 515 SturdyRefRestorer<LocalSturdyRefObjectId>& restorer) {
cannam@148 516 return RpcSystem<VatId>(network, restorer);
cannam@148 517 }
cannam@148 518
cannam@148 519 template <typename VatId, typename ProvisionId,
cannam@148 520 typename RecipientId, typename ThirdPartyCapId, typename JoinResult>
cannam@148 521 RpcSystem<VatId> makeRpcClient(
cannam@148 522 VatNetwork<VatId, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>& network) {
cannam@148 523 return RpcSystem<VatId>(network, nullptr);
cannam@148 524 }
cannam@148 525
cannam@148 526 template <typename VatId, typename ProvisionId,
cannam@148 527 typename RecipientId, typename ThirdPartyCapId, typename JoinResult,
cannam@148 528 typename RealmGatewayClient, typename InternalRef, typename ExternalRef>
cannam@148 529 RpcSystem<VatId> makeRpcClient(
cannam@148 530 VatNetwork<VatId, ProvisionId, RecipientId, ThirdPartyCapId, JoinResult>& network,
cannam@148 531 RealmGatewayClient gateway) {
cannam@148 532 return RpcSystem<VatId>(network, nullptr, gateway.template castAs<RealmGateway<>>());
cannam@148 533 }
cannam@148 534
cannam@148 535 } // namespace capnp
cannam@148 536
cannam@148 537 #endif // CAPNP_RPC_H_