mojo/shell/shell.mojom - Issue 93793009: Implement ServiceManager

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: mojo/shell/shell.mojom

Issue 93793009: Implement ServiceManager (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: Accidental inclusion of adb_run change Created 7 years ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

OLD	NEW
(Empty)
	1 // Copyright 2013 The Chromium Authors. All rights reserved.

	2 // Use of this source code is governed by a BSD-style license that can be

	3 // found in the LICENSE file.

	4

	5 module shell {
	abarth-chromium 2013/12/15 22:54:10 So far we've been putting everything in the "mojo" So far we've been putting everything in the "mojo" module because these are core mojo services. That will save you some ugly "::shell" typing elsewhere. It also will avoid the problem of having both ::shell and ::mojo::shell namespaces. DaveMoore 2013/12/16 17:40:22 Done, but I'd like to add the ability to put bindi Done, but I'd like to add the ability to put bindings in a nested namespace like "mojo::shell". On 2013/12/15 22:54:10, abarth wrote: Show quoted text > So far we've been putting everything in the "mojo" module because these are core > mojo services. That will save you some ugly "::shell" typing elsewhere. It > also will avoid the problem of having both ::shell and ::mojo::shell namespaces.
	6

	7 [Peer=ShellClient]

	8 interface Shell {

	9 // Loads url. mojo:{service} will result in the user of the value of the

	10 // --origin flag to the shell being used.

	11 void Connect(string url, handle<message_pipe> client_handle);

	12 };

	13

	14 [Peer=Shell]

	15 interface ShellClient {

	16 void AcceptConnection(handle<message_pipe> client_handle);

	17 };

	18

	19 }

OLD	NEW