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

Re: Wrapped implementations of XHR in script

From: Subbu Allamaraju <subbu.allamaraju@gmail.com>
Date: Fri, 13 Oct 2006 06:18:22 -0600
Message-ID: <e3f21b1a0610130518y3d2b3415hce9e6982d7f6a2f2@mail.gmail.com>
To: "Anne van Kesteren" <annevk@opera.com>
Cc: "Gorm Haug Eriksen" <gormer@opera.com>, "Web APIs WG (public)" <public-webapi@w3.org>
> The former doesn't really help interoperability, the latter has never been
> a goal.

I thought so. Nevertheless I'm bringing this up since it seems valuable.
Consider this scenario.

a. An app is written using some JSF component toolkit that uses XHR for most
of its functionality. The toolkit uses a factory to fetch an instance of

b. The app is now being aggregated (at the UI level) into another app.

The mechanism I described in the use case would let the first app work
stand-alone (a) or aggregated (b), without modifications. In the case of
(a), the app would get a native/default impl of XHR. In the case of (b), the
aggregating app would provide a script implementation of XHR.


Received on Friday, 13 October 2006 12:18:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:22 UTC