W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2003

Re: Support properties on interfaces

From: Joseph Kesselman <keshlam@us.ibm.com>
Date: Tue, 1 Jul 2003 09:33:37 -0400
To: www-dom@w3.org
Message-ID: <OF50C57054.4CC44948-ON85256D56.0049D01E-85256D56.004A7D3E@us.ibm.com>





See the standard Java and Javascript bindings included with the DOM spec
(and the non-standardized bindings available from other sources) for
specific examples of how the abstract IDL concepts of "interface" and
"property" are typically converted into actual callable APIs.

Generally, an interface maps to whatever the specific language offers as a
completely abstract class/interface/object-API.  If the language can't
offer that, the binding has to come up with some equivalent way to
reference the objects.

Generally, a property will be mapped to a getter method, a setter method,
or both... but it may map to field access in some bindings. Again, this
depends on the characteristics of the language you're developing the
binding for.

______________________________________
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"The world changed profoundly and unpredictably the day Tim Berners Lee
got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
Received on Tuesday, 1 July 2003 09:45:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:13:57 GMT