ISSUE-73 - Public View

Are we going to support non-ECMAScript languages?

State:
CLOSED
Product:
XMLHttpRequest
Raised by:
Anne van Kesteren
Opened on:
2006-04-06
Description:
Are we? If so, the main problem, besides ISSUE-72, is how to create an instance
of the object. From what I recall from the discussions we have several options:

(a) Leave it up to the language
(b) Create a method on some object (like Window or Document) that returns an
    the object.
(c) Do it through DOMImplementation

Given that (c) seems to be the most "correct" solution I favor that one.

Note: Some of these links may be accessible only to W3C Members.

Related emails:
  1. ISSUE-73: Are we going to support non-ECMAScript languages? (from dean+cgi@w3.org on 2006-04-06)
  2. Re: ISSUE-73: Are we going to support non-ECMAScript languages? (from ian@hixie.ch on 2006-04-06)
  3. Re: ISSUE-73: Are we going to support non-ECMAScript languages? (from cam@mcc.id.au on 2006-04-07)
  4. Re: ISSUE-73: Are we going to support non-ECMAScript languages? (from ian@hixie.ch on 2006-04-07)
  5. Re: ISSUE-73: Are we going to support non-ECMAScript languages? (from mjs@apple.com on 2006-04-06)
  6. Re: ISSUE-73: Are we going to support non-ECMAScript languages? (from ian@hixie.ch on 2006-04-07)
  7. Re: ISSUE-73: Are we going to support non-ECMAScript languages? (from jonas@sicking.cc on 2006-04-10)
  8. Re: ISSUE-73: Are we going to support non-ECMAScript languages? (from mjs@apple.com on 2006-04-10)
  9. Re: ISSUE-73: Are we going to support non-ECMAScript languages? (from cam@mcc.id.au on 2006-04-11)
  10. Re: ISSUE-73: Are we going to support non-ECMAScript languages? (from jonas@sicking.cc on 2006-04-10)
  11. Rabat f2f minutes, Monday afternoon, session 1 (from distobj@acm.org on 2006-09-19)

Related notes:

2006-09-18: Closed at Rabat f2f - will create Java package name, but not otherwise support non-ECMAscript languages