Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 38986 invoked from network); 30 Aug 2007 08:04:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Aug 2007 08:04:20 -0000 Received: (qmail 45469 invoked by uid 500); 30 Aug 2007 08:04:15 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 45130 invoked by uid 500); 30 Aug 2007 08:04:14 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 45121 invoked by uid 99); 30 Aug 2007 08:04:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Aug 2007 01:04:14 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mario@ops.co.at designates 194.152.182.5 as permitted sender) Received: from [194.152.182.5] (HELO mgate.ops.co.at) (194.152.182.5) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Aug 2007 08:05:09 +0000 Received: from smtp.ops.co.at (smtp.int.ops.co.at [172.27.0.4]) by mgate.ops.co.at (OPS Mail Gateway - authorized use only - NO UCE/UBE C=AT L=VIE) with ESMTP id 73F392828E for ; Thu, 30 Aug 2007 10:03:49 +0200 (CEST) Received: by smtp.ops.co.at (Postfix, from userid 65534) id 2C3176E0BA8; Thu, 30 Aug 2007 10:03:48 +0200 (CEST) Received: from [172.27.1.104] (lints2.int.ops.co.at [172.27.1.104]) by smtp.ops.co.at (Postfix) with ESMTP id B482D6E0BA6 for ; Thu, 30 Aug 2007 10:03:47 +0200 (CEST) Message-ID: <46D679E4.3070805@ops.co.at> Date: Thu, 30 Aug 2007 10:03:48 +0200 From: Mario Ivankovits User-Agent: Thunderbird 2.0.0.0 (X11/20070418) MIME-Version: 1.0 To: Jakarta Commons Developers List Subject: [vfs] Re: Specifying options to FTP etc.. References: <46D535B4.4020202@wso2.com> <46D5396D.6000801@ops.co.at> <46D57E82.6020500@wso2.com> In-Reply-To: <46D57E82.6020500@wso2.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on smtp.ops.co.at X-Spam-Level: X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, hits=-12.8 required=7.0 tests=AWL,BAYES_00, LOCAL_SPAMDOMAINS1,LOCAL_URI_FOUND,RATWR10_MESSID autolearn=no version=2.64 Hi! > I don't quite agree with this - this may be the common case for HTTP, > but the URI spec does not enforce it. Ok, but how should we differentiate between these both use-cases? If we would like to allow this style of URL we need some special delimiter to know what to pass to VFS as configuration and what to pass further to the server. And no - I don't want to care if we are using the HTTP or any other scheme. Hmmm ..... what we can do might be something like this. We add a new resolveFile method to the FileSystemManager interface: FileObject resolveFileWithUrlConfiguration(String uri) and we separate the VFS configuration using the double question-mark (??) A url like: http://www/path/cgi-bin/send.pl?FILE=ABC&TYPE=PDF??proxyHost=proxy.host&proxyPort=8080 will work then. resolveFileWithUrlConfiguration will strip the part after (including) ?? and create the FileSystemOption stuff (if possible) which means the vfs configuration string will not be shown in the filename. Then FileObject fo = manager.resolveFileWithUrlConfiguration(....); FileObject fo2 = manager.resolveFileWithUrlConfiguration(fo.getName().toString); will not use the same filesystem configuration. This limitation makes it look a little bit hacky - we might remove this limitation later. What do you think? Ciao, Mario --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org