diff options
author | viettrungluu@chromium.org <viettrungluu@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-12-02 18:51:43 +0000 |
---|---|---|
committer | viettrungluu@chromium.org <viettrungluu@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-12-02 18:51:43 +0000 |
commit | 072b8d48705dc76cafa1aa8189f62a15c94aa7fb (patch) | |
tree | dd7a5775219f8eb6db11ad1af704338c194b7fce /rlz/chromeos | |
parent | db8e86cd38613b11de6efd70af60138491bcf08c (diff) | |
download | chromium_src-072b8d48705dc76cafa1aa8189f62a15c94aa7fb.zip chromium_src-072b8d48705dc76cafa1aa8189f62a15c94aa7fb.tar.gz chromium_src-072b8d48705dc76cafa1aa8189f62a15c94aa7fb.tar.bz2 |
Mojo: Create a PlatformChannel abstraction.
PlatformChannel abstracts the *creation* of a (bidirectional) "OS
pipe"/"channel", and will (soon) also provide a platform-independent way
of passing such a channel to a (new) child process.
It intentionally does not abstract away the *use* of such a channel,
which will still require using native primitives (via a native OS
handle, thinly wrapped by the existing PlatformChannelHandle).
Note that though channels are bidirectional and are functionally
symmetric, there are nonetheless "server" and "client" ends. This is to
accomodate setups where there is such a distinction at the OS level (and
in particular, setups where channels are named OS objects).
R=darin@chromium.org, darin
Review URL: https://codereview.chromium.org/92563002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@238141 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'rlz/chromeos')
0 files changed, 0 insertions, 0 deletions