WebAPI/WebTelephony: Difference between revisions

WebAPI/WebTelephony (view source)

Revision as of 23:55, 1 December 2011

20 bytes added , 1 December 2011

→‎Proposed API

Sicking

Confirmed users

716

edits

@@ Line 4: / Line 4: @@
    interface Telephony : EventTarget {
+    TelephonyCall dial(DOMString number); // Returns a object in "dialing" state
      attribute boolean muted;           // Should these live on the call/group?
      attribute boolean speakerOn;
@@ Line 24: / Line 25: @@
    }
-  [Constructor(DOMString)]
    interface TelephonyCall : EventTarget {
      readonly attribute DOMString number;
-     readonly attribute DOMString readyState; // "calling", "incomming", "connected", "closed", "busy"
+     readonly attribute DOMString readyState;
-    // Can we get info on when a call goes from "trying to place call" to "calling"?
+    // "dialing", "ringing", "busy", "connecting", "connected", "disconnecting", "disconnected", "incoming"
-     attribute Function onconnect;
-     attribute Function ondisconnect;
+     attribute Function onreadystatechange;
+     attribute Function onringing;
      attribute Function onbusy;
+    attribute Function onconnecting;
-     attribute CallGroup? group;
+    attribute Function onconnected;
+    attribute Function ondisconnecting;
+     attribute Function ondisconnected;
      void answer(); // Should this make the call the active one?
      void disconnect();
-     // void hold(); Not sure if needed for now. We might need to remake group APi to make it async
+     // void hold(); These need to be made async. Also not sure if they are needed with a proper async 3-way API
      // void resume();
-  }
-  [Constructor()]
-  interface CallGroup {
-    TelephonyCall item(unsigned long index);
-    readonly attribute unsigned long length;
    }