- From: Marcos Caceres <marcosc@opera.com>
- Date: Mon, 8 Jun 2009 20:34:14 +0200
- To: Marcin Hanclik <Marcin.Hanclik@access-company.com>
- Cc: Scott Wilson <scott.bradley.wilson@gmail.com>, Henri Sivonen <hsivonen@iki.fi>, public-webapps <public-webapps@w3.org>
2009/6/2 Marcin Hanclik <Marcin.Hanclik@access-company.com>: > Hi Scott, > > In BONDI we have discussed the (has/request)Feature() for some time. > http://bondi.omtp.org/1.0/security/BONDI_Architecture_and_Security_v1.0.pdf, section 4.3 > > A few points for further discussion: > 1. feature (at least in BONDI) is an abstract thing, not just one function. So hasFeature() is simply optimized checking procedure. If you check for a feature and discover that it is available, you may/should/must assume that a set of functions is available. Otherwise, you have to check each function individually and basically you cannot assume that if one functions is available, then the other is as well. > > 2. requestFeature() adds dynamism to the Website content. Widgets express their dependency statically by <feature>. > http://bondi.omtp.org/1.0/security/BONDI_Architecture_and_Security_Appendices_v1.0.pdf B.2 specifies more details. > I still have no clue what requestFeature() does/means. The again, I have not read the Bondi spec regarding that. -- Marcos Caceres http://datadriven.com.au
Received on Monday, 8 June 2009 18:34:55 UTC