W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2009

Re: [widgets] What does it mean to have an unavailable API

From: Marcos Caceres <marcosc@opera.com>
Date: Mon, 8 Jun 2009 20:34:23 +0200
Message-ID: <b21a10670906081134l230ebf57g3eafdf0ff920922a@mail.gmail.com>
To: Marcin Hanclik <Marcin.Hanclik@access-company.com>
Cc: Jonas Sicking <jonas@sicking.cc>, Scott Wilson <scott.bradley.wilson@gmail.com>, Henri Sivonen <hsivonen@iki.fi>, public-webapps <public-webapps@w3.org>
2009/6/3 Marcin Hanclik <Marcin.Hanclik@access-company.com>:
> Hi Marcos,
>
> requestFeature() from BONDI 1.0 is an asynchronous API that follows API design pattern:
> http://bondi.omtp.org/1.0/apis/BONDI_Interface_Patterns_v1.0.html#asynchronicity
> requestFeature() is described in detail in:
> http://bondi.omtp.org/1.0/security/BONDI_Architecture_and_Security_v1.0.pdf
> section 4.3.2
>
> "A call to the successCallback Function signifies that the request has been satisfied and that the corresponding JavaScript API is immediately available."
>

Ok.

> It means basically that you can directly use the requested API if the request to have it was successful.
> You do not have to perform any further checks and there is actually a bunch of interfaces that are available, not just a single object.
>

Right. However, I don't know why we are discussing this if, as you
said before, it has no relevance to widgets.


-- 
Marcos Caceres
http://datadriven.com.au
Received on Monday, 8 June 2009 18:35:00 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:31 GMT