Return-Path: X-Original-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 670079114 for ; Fri, 17 Feb 2012 20:33:41 +0000 (UTC) Received: (qmail 86514 invoked by uid 500); 17 Feb 2012 20:33:41 -0000 Delivered-To: apmail-incubator-callback-dev-archive@incubator.apache.org Received: (qmail 86482 invoked by uid 500); 17 Feb 2012 20:33:41 -0000 Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: callback-dev@incubator.apache.org Delivered-To: mailing list callback-dev@incubator.apache.org Received: (qmail 86472 invoked by uid 99); 17 Feb 2012 20:33:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Feb 2012 20:33:41 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of dave.c.johnson@gmail.com designates 209.85.216.54 as permitted sender) Received: from [209.85.216.54] (HELO mail-qw0-f54.google.com) (209.85.216.54) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Feb 2012 20:33:34 +0000 Received: by qaea17 with SMTP id a17so4626102qae.6 for ; Fri, 17 Feb 2012 12:33:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=zVSap8wtzR28OEURlBtcL0OPKvFouDaJUyhXIfSHREE=; b=xjH/e9WCaPTeKalBtekxV2Iomf86XRJmfKm2RhUU03ZfJb8gk+pBKnN7pTLwLMODDj 7fE57oGZgDJ4y6h3MFbVWHQ0jYr5hvzCvRHtKWzZqxg8KCLr2iLuVHmIc5t4Ja8+oPKC cwGlOVXak2hCebH58fCHYKkNJbnh6lCht0Lts= MIME-Version: 1.0 Received: by 10.229.69.30 with SMTP id x30mr5517235qci.97.1329510793504; Fri, 17 Feb 2012 12:33:13 -0800 (PST) Received: by 10.229.160.210 with HTTP; Fri, 17 Feb 2012 12:33:13 -0800 (PST) In-Reply-To: References: Date: Fri, 17 Feb 2012 12:33:13 -0800 Message-ID: Subject: Re: Changes to File API From: Dave Johnson To: "callback-dev@incubator.apache.org" Content-Type: multipart/alternative; boundary=00032557bc5a92684304b92eda95 X-Virus-Checked: Checked by ClamAV on apache.org --00032557bc5a92684304b92eda95 Content-Type: text/plain; charset=ISO-8859-1 For all of these sorts of changes lets endevour to maintain backwards compatibility and put in deprecation notices. Ideally the deprecated APIs are removed at a major version change, e.g. when we hit 2.0. On Friday, February 17, 2012, Filip Maj wrote: > I like that idea, Simon. Simple to add a method copy from toURL -> toURI, > add a console.log, tag for 1.5, done. > > As for updating the error codes - can we shelve that for 1.6? > > On 12-02-17 11:52 AM, "Simon MacDonald" > > wrote: > > >For the 1.5.0 release can we support .toURI() and .toURL()? > >We'll mark toURI as deprecated and remove it in 1.6.0 or 1.7.0. What do > >you > >think? > > > >As for the FileError codes. Grrrrr...why did they have to change them. > > > >Simon Mac Donald > >http://hi.im/simonmacdonald > > > > > >On Fri, Feb 17, 2012 at 2:36 PM, Becky Gibson > >>wrote: > > > >> I was running the mobile-spec after Shaz completed and checked in the > >>iOS > >> name change (THANKS, Shaz!) and found that several file tests fail. The > >> issue is the name change of the .toURI() api to .toURL(). > >> Checking on the W3C File API: Directories and Systems spec. this API was > >> indeed renamed from the October, 2010, version of the spec that we > >> implemented to the April and May, 2011 versions. The FileError codes > >>have > >> also been reassigned - although that has not been updated in the > >>unified-js > >> implementation. > >> > >> Other than the API name change and FileError code reassignments, I don't > >> see major changes in the specification. However, this will certainly > >>break > >> existing apps and I question making that change. I realize it has to > >>be > >> made sooner or later, but it might be best to wait for the api to be > >> finalized. If we are going to make this api change, then we should > >> probably also make the FileError changes to be consistent. And update > >>the > >> docs and make sure this is well documented. > >> > >> my two cents, > >> -becky > >> > > --00032557bc5a92684304b92eda95--