[RTW] Non-IETF work: Coming up with a high level API spec

[Harald Alvestrand]

Of course it turned out that I had overlooked a corporate security 
policy. While I can share a document to individual accounts, I can't 
publish it for everyone to look at.

The document is attached.

                    Harald

On 03/24/11 20:29, Harald Alvestrand wrote:
> Despite the fact that it's getting very close to our BOF session, 
> other things are happening....
>
> I've been working with some other people on getting together a 
> specification for a very-high-level Javascript API for media control.
> This is intended as an "easy to use" API for those who do not wish to 
> put detailed control in Javascript, and allows to build applications 
> without getting into signalling protocols - those can be handled at 
> server side if needed, or by other libraries if needed / possible.
>
> It's roughly at the same level as the just published WHATWG 
> PeerConnection API or the now-gone ConnectionPeer API, and many 
> functions are identical, but there are some differences.
>
> The spec is here:
>
> https://docs.google.com/a/google.com/document/pub?id=1_lFKBgjNMVy98TMZT0kZ67RD57j1aL7ldPzv5zcJpgw 
>
>
> It does not specify a format for sending data, since I believe we do 
> not have consensus on even the design constraints for this - there are 
> also other parts that are not fully fleshed out.
>
> Feedback welcome. If people want edit permission, so that they can 
> enter comments directly into the document, pass me your google account 
> info.
>
>                        Harald
> _______________________________________________
> RTC-Web mailing list
> RTC-Web at alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/rtc-web
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: rtcsession-api.pdf
Type: application/pdf
Size: 292464 bytes
Desc: not available
URL: <http://www.alvestrand.no/pipermail/rtc-web/attachments/20110324/04d901a9/attachment-0001.pdf>