Lines Matching refs:invitation

397 between them. An invitation must be transmitted over some platform-specific IPC
414 #include "mojo/public/cpp/system/invitation.h"
422   mojo::OutgoingInvitation invitation;
427       invitation->AttachMessagePipe("arbitrary pipe name");
435   OutgoingInvitation::Send(std::move(invitation), child_process.Handle(),
449 #include "mojo/public/cpp/system/invitation.h"
462   // Accept an invitation.
463   mojo::IncomingInvitation invitation = mojo::IncomingInvitation::Accept(
467       invitation->ExtractMessagePipe("arbitrary pipe name");
482 mojo::OutgoingInvitation invitation;
483 auto pipe = invitation->AttachMessagePipe("x");
489 auto invitation = mojo::IncomingInvitation::Accept(...);
490 auto pipe = invitation->ExtractMessagePipe("x");
497 And just to be sure, the usage here could be reversed: the invitation sender
502 Accepting an invitation admits the accepting process into the sender's connected
520 incoming invitation.
530 processes already belong to a network. In this case, an **isolated** invitation
535 Once a connection is established via isolated invitation, Mojo IPC can be used