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

Side by Side Diff: chrome/common/extensions/dial_device_description_parser.mojom

Issue 2745653008: [Media Router] Parse device description xml in utility process (Closed)
Patch Set: use mojo instead of IPC Created 3 years, 9 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
(Empty)
1 // Copyright 2017 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 // DIAL device description parsing interface provided by the utility process and
6 // exposed by mojo policy control to the chrome browser process.
7
8 module extensions.mojom;
mark a. foltz 2017/03/17 19:05:47 Is this going to be used only from extensions? It
zhaobin 2017/03/18 00:17:39 Moved mojo related files to common/media_router/.
9
10 struct DialDeviceDescription {
mark a. foltz 2017/03/17 19:05:47 Can you document the meanings of these fields, may
zhaobin 2017/03/18 00:17:38 Done.
11 string unique_id;
12 string friendly_name;
13 string model_name;
14 string device_type;
15 };
16
17 interface DialDeviceDescriptionParser {
18 // Parses |device_description_xml_data| to get device description data. If
19 // parsing succeeds, invokes callback with |parse_result| equals to true;
20 // otherwise invokes callback with |parse_result| equals to false.
21 // |device_description|: device description object. Empty if parsing fails.
22 // |logging_xml|: xml file for logging without unique ID and serial number.
23 ParseDialDeviceDescription(string device_description_xml_data)
24 => (bool parse_result,
25 DialDeviceDescription device_description,
26 string logging_xml);
27 };
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698