Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of tommy@devgeeks.org designates
 74.125.82.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CADVgkyNDHQU9aOBWpFB1wOf9HnaXuzWjTQyVS7kfUDddz3oH2w@mail.gmail.com>
References: 
 <CAK_TSXKZd+NWjzDdJfigNs35P7kNCym+6GnFTC75vTYVOOpJUg@mail.gmail.com>
	<CADVgkyNDHQU9aOBWpFB1wOf9HnaXuzWjTQyVS7kfUDddz3oH2w@mail.gmail.com>
Date: Tue, 19 Nov 2013 10:51:47 +1100
Message-ID: 
 <CAPTyS6CdFBRYYyUOPFzbdmWN_WHOy8x4CnFB6iejaDC=DOjP3w@mail.gmail.com>
Subject: Re: Updating FileTransfer
From: Tommy Williams <tommy@devgeeks.org>
To: dev@cordova.apache.org
Content-Type: multipart/alternative; boundary=001a11c283b81fc30d04eb7c3b2d

--001a11c283b81fc30d04eb7c3b2d
Content-Type: text/plain; charset=ISO-8859-1

I'll hate you, but I guess I'll get over it (I have a plugin that is
basically a modified fork of file-transfer.. . gonna be a pain updating it
now, heh).

What happened to the suggestions for this all being a new plugin of some
kind? Though plugins are versioned, an old version gets no bug fixes...
On 19/11/2013 9:11 AM, "Brian LeRoux" <b@brian.io> wrote:

> Answers inline.
>
>
> > Does FileTransfer implement any published standard, or is it our own API?
> >
> > Nope.
>
>
>
> > Does it make sense for FileTransfer to continue to use raw FileSystem
> paths
> > (and *not* go through File at all?) given that the File API will soon be
> > returning only relative paths and filesystem:// URLs.
> >
> > Consistent w/ URL scheme makes sense to me but I'll let others chime in
> how this will break everything and our users will hate us. But remember:
> plugins are versioned!
>

--001a11c283b81fc30d04eb7c3b2d--