- From: Cullen Jennings <fluffy@cisco.com>
- Date: Sun, 1 Jan 2012 11:08:09 +1100
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: Harald Alvestrand <harald@alvestrand.no>, public-webrtc@w3.org, hta@google.com
On Dec 31, 2011, at 3:19 , Tab Atkins Jr. wrote: > On Thu, Dec 29, 2011 at 12:47 AM, Cullen Jennings <fluffy@cisco.com> wrote: >> I'll note that using strings instead of integers is somewhat crappy when an API call needs to be mapped to ENUMs in other programming languages such as C. > > We've moved away from caring about languages other than Javascript > when designing web APIs; years of struggling with the turgid horror of > the original DOM (designed for easy compat with Java) taught us that > lesson. ^_^ This is a large part of the reason why we created WebIDL > rather than just continuing to use IDL. > > That said, if an API like this does need to be expressed in another > language where enums are more natural than strings, there's nothing > wrong with defining an enum in their binding. It should just stay out > of the web-facing API binding, which is meant to favor JS. > > ~TJ Thanks - makes sense
Received on Sunday, 1 January 2012 00:08:42 UTC