Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Message-ID: <3EC40BD0.7070502@anthonyeden.com>
Date: Thu, 15 May 2003 17:51:12 -0400
From: Anthony Eden <me@anthonyeden.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.3) Gecko/20030312
MIME-Version: 1.0
To: Jakarta Commons Users List <commons-user@jakarta.apache.org>
Subject: Re: [VFS] [PATCH] UrlFileObject.exists (when HTTP)
References: <00e001c31af8$bc595ad0$35c5ea43@wdn086>
 <200305160650.08139.adammurdoch@apache.org>
In-Reply-To: <200305160650.08139.adammurdoch@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Adam Murdoch wrote:

>On Fri, 16 May 2003 01:43 am, Adam Jack wrote:
>  
>
>>I tell ya, I'd love to replace this code with HttpClient code, where we
>>could (1) set the UserAgent to be 'commons-vfs' (2) user HEAD and/or GET
>>(3) have "follow redirects work" (I found a bug in JDK java.net.URL where
>>it does not seem to follow relative redirects) and (4) only do (at most) on
>>HEAD and one GET (if needed) per URL. [4 could be done with either
>>underlying code.]
>>    
>>
>
>These are all good ideas.  My plan for doing this was to extend the WebDAV 
>provider to handle plain HTTP as well, since it already sits on top of 
>HttpClient, and already does these things (uses OPTIONS instead of HEAD).  It 
>just needs to be extended to handle non-dav resources.
>
I would rather have it work the other way around - the WebDAV provider 
should extend the plain URL provider, or they should be kept separate.  
I don't want to have to have WebDAV libraries if I am not using that 
functionality.

Sincerely,
Anthony Eden