- From: Robin Berjon <robin@berjon.com>
- Date: Mon, 6 Jul 2009 16:18:36 +0200
- To: Jonas Sicking <jonas@sicking.cc>
- Cc: WebApps WG <public-webapps@w3.org>
Heya Jonas,
On Jun 30, 2009, at 10:38 , Jonas Sicking wrote:
> However, what is the use case for all this power? I.e. what
> application would want to do this? The downside of having all the
> power and features of using events is that the syntax becomes more
> complex. So we should only do it if it provides features that people
> actually need.
I haven't yet given this a lot of thought, but one reason I can see
for supporting events is extensibility. Remember that the upcoming DAP
WG will develop some manner of file system API. It would be really,
really nice if it could just reuse the interfaces from this spec. But
it is likely to be more powerful, and therefore might require (or at
least benefit from) greater flexibility in notification.
Let's say for instance we add delete(), one might want:
file.addEventListener("delete", delCB, false);
My brain's still warming up after a week in babyland, but I think we
should look at DAP use cases before coming to a conclusion on the most
useful notification mechanism.
--
Robin Berjon - http://berjon.com/
Feel like hiring me? Go to http://robineko.com/
Received on Monday, 6 July 2009 14:19:16 UTC