[PresentationAPI] Plumbing send() from PresentationSession IDL to platform/.

Source/modules/presentation/PresentationSession.idl

Index: Source/modules/presentation/PresentationSession.idl
diff --git a/Source/modules/presentation/PresentationSession.idl b/Source/modules/presentation/PresentationSession.idl
index 8c942763ef22737a5cb17ec26fca1f6766f1c15e..08f82ed4736d373620a11af7279889763b4d13bb 100644
--- a/Source/modules/presentation/PresentationSession.idl
+++ b/Source/modules/presentation/PresentationSession.idl
@@ -16,7 +16,10 @@ enum PresentationSessionState {
     readonly attribute DOMString? id;
     readonly attribute PresentationSessionState state;
 
-    void postMessage(DOMString message);
+    [RaisesException] void postMessage(DOMString message);
+    [RaisesException] void postMessage(Blob data);
+    [RaisesException] void postMessage(ArrayBuffer data);
+    [RaisesException] void postMessage(ArrayBufferView data);

[Peter Beverloo, 2015/03/25 20:20:29]

I don't see why we need these overloads. I would consider postMessage(DOMString)
to be a mere placeholder?

Other postMessage implementations in Blink follow this signature:

    void postMessage(any message, optional sequence<> transferables);

Since a session is a remote target I can understand that you don't want the
transferables, but rather than having all these overloads can we use "any data"
or the newer "SerializedScriptValue data"? Do we envision this could cause
issues deserializing by the recipient? In that case I would be curious to learn
how this would work well for Blobs.

[USE s.singapati at gmail.com, 2015/03/26 11:57:40]

Acknowledged. I think we try to be consistent with WebRTC as commented by
avayvod. 

     void close();
 
     attribute EventHandler onmessage;