W3C home > Mailing lists > Public > public-webapi@w3.org > March 2006

ISSUE-44: XHR: Overloading in the IDL

From: Web APIs Issue Tracker <dean+cgi@w3.org>
Date: Sun, 19 Mar 2006 22:13:25 +0000 (GMT)
To: public-webapi@w3.org
Message-Id: <20060319221325.9D5FC33201@kearny.w3.org>


ISSUE-44: XHR: Overloading in the IDL

http://www.w3.org/2005/06/tracker/webapi/issues/44

Raised by: Bjoern Hoehrmann
On product: XMLHttpRequest

The current draft does not say which "IDL" is used to define the XHR
interface, but as far as I can tell overloading is not allowed in OMG
IDL. We need to either explain this in the document or change the IDL
such that the conflicts are removed. The later can be achieved with

  void open(... all arguments here ...);
  void send(in DOMObject data) ...;

Where the implications are explained in the member definitions and
the language bindings as appropriate, so this is a change in form
only. .setParameter in Core does something similar to what I propose
for send(), optional parameters are new in the DOM-like W3C APIs. In
addition, there should be clear reference to the IDL specification.

Shouldn't send() raise an exception if the method does not support
the type of data passed to it, btw?
Received on Sunday, 19 March 2006 22:13:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:54 GMT