Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 71045 invoked from network); 18 Apr 2009 14:48:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Apr 2009 14:48:07 -0000 Received: (qmail 32607 invoked by uid 500); 18 Apr 2009 14:48:06 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 32482 invoked by uid 500); 18 Apr 2009 14:48:06 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 32472 invoked by uid 99); 18 Apr 2009 14:48:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Apr 2009 14:48:06 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of vlsergey@gmail.com designates 209.85.219.160 as permitted sender) Received: from [209.85.219.160] (HELO mail-ew0-f160.google.com) (209.85.219.160) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Apr 2009 14:47:58 +0000 Received: by ewy4 with SMTP id 4so1258591ewy.42 for ; Sat, 18 Apr 2009 07:47:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:from:date:message-id :subject:to:content-type; bh=lL6PmIrC/iie099W+IHuA44i/HPjTdy7+EA/6L1n+1E=; b=iOiApPhr8G+Ll86HBTuyt8jrjgn587DTvibpZ45hDQQwl1RX9wbAm6auzAo6f1Qqa9 f0MR7hFEslPejHizurSViVXkl1o0Hj30ZBJfMCacqpGDKS1L0HNgTSC8dUW4cT4y8pQZ 7GowThwuCboiEGaYJHJVrzg/U5i48rWMlABqo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=LUBzp+8dwve1WIhsvV1eF/6BeKPviIxH7hU+zoZGAxp084dtJVN5pGdRWYvjfC8xqo tKtrHET6adLuR+Ff10pME1x4Ya8ZtHppneRWIodvcnE94p8FrCEHVKOVnLkB540n8cXb nlatmh3IiN2ssvQmc7Msq56Vj9++Rb6eTL7Gw= MIME-Version: 1.0 Received: by 10.210.136.10 with SMTP id j10mr1817105ebd.7.1240066058094; Sat, 18 Apr 2009 07:47:38 -0700 (PDT) From: Sergey Vladimirov Date: Sat, 18 Apr 2009 18:47:23 +0400 Message-ID: <18e049e20904180747k107e671am550500376405e27a@mail.gmail.com> Subject: [Commons-VFS] Use URI as FileName holder. Was: Re: Commons-VFS SVN commit permission To: Commons Developers List Content-Type: multipart/alternative; boundary=0015174bdeaae407d60467d56053 X-Virus-Checked: Checked by ClamAV on apache.org --0015174bdeaae407d60467d56053 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mario, In most cases GenericFileName or LocalFileName is used. Both of them can be represented as "native" URI. LayeredFileName (the one with "!" syntax) can't be used with "native" URI, of course. It's still possible to use URI as internal storage for GeneriFileName and get rid of several methods, that have similar functionality from JDK. Including, but not limited to, parsing and string representation building. -- Sergey. On Thu, Apr 16, 2009 at 8:27 PM, Mario Ivankovits wrote: > Hi! > > > > Have an idea to change FileName implementation to use Java's > > > internal URI, > > > and it need to be discussed first. 2.0 release may be the only good > > > point to > > > do that in next few years :) > > > > > > > There are a bunch of places where URI should have been used. > > Please keep in mind that VFS is able to use "nested" URIs, e.g. > tar:gz:file:// etc. > Is this doable with Javas URI class? > > Ciao, > Mario > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > For additional commands, e-mail: dev-help@commons.apache.org > > -- Sergey Vladimirov --0015174bdeaae407d60467d56053--