- From: Kenneth Rohde Christiansen <kenneth.r.christiansen@intel.com>
- Date: Mon, 18 Feb 2013 10:50:16 +0100
- To: Mounir Lamouri <mounir@lamouri.fr>
- Cc: public-sysapps@w3.org
Hi there,
> Examples Jonas showed using DOMFuture could just work with DOMRequest if
> we add this .then() method.
>
> Also, we could imagine stuff like:
> getSomeData().then(function(data) {
> return getDataRelatedToThoseData(data);
> }).then(function(data) {
> show(data);
> });
>
> I have a patch for Gecko implementing that.
I like this pattern. It also seems closer to what MS are using in
their Windows 8 JS APIs.
> However, we shouldn't spend too much time debating that. My point is
> just that DOMRequest vs DOMFuture is not a discussion. One is just the
> other with some additions, they have incompatibility except the naming
> of some attributes and events.
>
> I think we should discuss if DOM{Future,Promise} should have DOM events,
> if we should just add a Future type in Javascript, etc.
> But that discussion should probably happen outside of that group?
Yes, at least I think we need to include the webapps WG.
Cheers
Kenneth
>
> Cheers,
> --
> Mounir
>
--
---------------------------------------------------------------------
Intel Denmark Aps
Langelinie Alle 35, DK-2100 Copenhagen
CVR No. 76716919
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
Received on Monday, 18 February 2013 09:51:10 UTC