W3C home > Mailing lists > Public > public-device-apis@w3.org > August 2009

RE: ISSUE-4: Versioning Straw Poll

From: <richard.tibbett@orange-ftgroup.com>
Date: Thu, 27 Aug 2009 15:27:01 +0200
Message-ID: <355A518BC0575547B2A3D6773AAF8EEF34078E@ftrdmel1>
To: <robin@robineko.com>, <public-device-apis@w3.org>
> On Thu, 27 Aug 2009 14:48:59 +0200, Robin Berjon <robin@robineko.com>
> wrote:
> > Here's the SP:
> >
> >    This house believes that explicit version mechanisms on 
> an API, such
> >    as have been done elsewhere using for instance 
> hasFeature(), a version
> >    attribute on interface object, or a version parameter passed to a
> >    constructor are not useful in a web context and should 
> be forsaken.
> >    Future revisions to given interfaces should either be strictly
> >    additive,
> >    change names, or ensure that what limited deltas are 
> made do not break
> >    real-world code.

I agree.

(NB: this is the opinion of my company based on previous internal
discussion, hence the quick response)


----------
|        |   Rich Tibbett
|        |   Orange Labs UK :: Service Evolution :: Research Engineer
| orange |   E: richard.tibbett@orange-ftgroup.com
----------   
Received on Thursday, 27 August 2009 13:27:48 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:38 UTC