Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(6)

Side by Side Diff: services/android/intent_receiver.mojom

Issue 1116653002: Introduce authentication service. (Closed) Base URL: https://github.com/domokit/mojo.git@master
Patch Set: Created 5 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 // Copyright 2015 The Chromium Authors. All rights reserved. 1 // Copyright 2015 The Chromium Authors. All rights reserved.
2 // Use of this source code is governed by a BSD-style license that can be 2 // Use of this source code is governed by a BSD-style license that can be
3 // found in the LICENSE file. 3 // found in the LICENSE file.
4 4
5 [JavaPackage="org.chromium.mojo.intent"] 5 [JavaPackage="org.chromium.mojo.intent"]
6 module intent_receiver; 6 module intent_receiver;
7 7
8 // Service to interact with android intents. 8 // Service to interact with android intents.
9 interface IntentReceiverManager { 9 interface IntentReceiverManager {
10 // This method takes an |IntentReceiver| and returns a serialized intent. 10 // This method takes an |IntentReceiver| and returns a serialized intent.
11 // The serialized intent can be deserialized using an android parcel. The 11 // The serialized intent can be deserialized using an android parcel. The
12 // caller can then transform this intent into a PendingIntent using 12 // caller can then transform this intent into a PendingIntent using
13 // |PendingIntent#getService| and send it to another android application. 13 // |PendingIntent#getService| and send it to another android application.
14 // Whenever the pending intent is executed, the receiver will be called with 14 // Whenever the pending intent is executed, the receiver will be called with
15 // the content of the received intent. To be noted: this will fail if the 15 // the content of the received intent.
16 // received intent is active (contains either a Binder or a file descriptor). 16 // To be noted, this will fail if the received intent is active (contains
17 RegisterReceiver(IntentReceiver receiver) => (array<uint8> intent); 17 // either a Binder or a file descriptor).
18 RegisterIntentReceiver(IntentReceiver receiver) => (array<uint8>? intent);
19
20 // This method takes an |IntentReceiver| and returns a serialized intent.
21 // The serialized intent can be deserialized using an android parcel. The
22 // caller can then add an intent it wants the system to send using
23 // |Activity#startActivityForResult| and then send it using
24 // |Context#startService|. Whenever the started activity sends a result, the
25 // receiver will be called with the content of the received intent. If the
26 // activity is cancelled, the receiver will be closed.
27 RegisterActivityResult(IntentReceiver receiver) => (array<uint8>? intent);
ppi 2015/04/29 13:32:23 Should this be called RegisterStartActivityForResu
tonyg 2015/04/29 13:47:43 [+alhaad] Just curious if this new API also helps
qsr 2015/04/29 14:22:19 I don't know for sure. It depends a lot on which A
qsr 2015/04/29 14:22:19 Renamed: RegisterActivityResultReceiver
18 }; 28 };
19 29
20 // Receiver interface, to be used with 30 // Receiver interface, to be used with |IntentReceiverManager|.
21 // |IntentReceiverManager.RegisterReceiver|.
22 interface IntentReceiver { 31 interface IntentReceiver {
23 OnIntent(array<uint8> intent); 32 OnIntent(array<uint8> intent);
24 }; 33 };
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698