Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of jason.dillon@gmail.com
 designates 64.233.162.204 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer:sender;
        b=mE6f+g23mpU3m9821aZbXGoI3BKHwi4R8uMFPA8cmziLwXesqdQ2ZU1eKtstLGHKWV3jWXZhExlw7SmTrHFEicajBp4Lw/GKidEVfuZbr07rGzbi00TZ6m9Yj/8E9ysDAS3mzbUNaO9GM/BjkFVxZ49T7mMfsW5fiURdlqIjh3M=
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <09B71F75-4456-4AA8-9AC7-A440E9DC0146@iq80.com>
References: <23D31F5E-5D27-4CB6-AC12-146C97FB9B96@gmail.com>
 <7B5F9309-69AD-459B-97F1-503A419345D2@iq80.com>
 <3C6E47B0-3695-4D95-BC7B-1BDD0F62401B@gmail.com>
 <26D09A82-5896-4029-ABE5-73B262D9FB3D@iq80.com>
 <14EA0336-C642-4071-87A3-42EE732C0CC2@planet57.com>
 <09B71F75-4456-4AA8-9AC7-A440E9DC0146@iq80.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <75786246-DF5B-46C0-A356-55CD18BFD3A1@planet57.com>
Content-Transfer-Encoding: 7bit
From: Jason Dillon <jason@planet57.com>
Subject: Re: GERONIMO-1526
Date: Mon, 21 Aug 2006 14:42:26 -0700
To: dev@geronimo.apache.org
Sender: Jason Dillon <jason.dillon@gmail.com>

I think it is fine to use File for now... its simpler... though I'd  
still like to entertain the idea of using VFS to abstract all things  
file...

--jason


On Aug 21, 2006, at 2:35 PM, Dain Sundstrom wrote:

> On Aug 21, 2006, at 1:39 PM, Jason Dillon wrote:
>
>> On Aug 21, 2006, at 1:31 PM, Dain Sundstrom wrote:
>>> I think using URLs instead of files, is going to be very  
>>> difficult.  We had tons of problems dealing with paths containing  
>>> spaces and urls.  IIRC we had to encode and decode URLs all the  
>>> time.  Also, some deployers need to scan the directories.  For  
>>> example, the RAR deployer needs to add all jar files in the  
>>> archive/directory to the class path.  In Jee5 ear files we need  
>>> to scan for all nested modules.
>>
>> Ya maybe... I was just thinking about deploying from things other  
>> than files, like an http:// address or nested jar, or some other  
>> custom protocol.  Using URL allows flexibility by abstraction...  
>> where using File binds you to files, since we have no way to  
>> augment them.
>
> I understand. Originally, I wanted the deployers to work that way  
> also.  Then after reading the source for URL, it occurred to me  
> that the VM downloads the content to the local file system anyway,  
> so if we download them ourselves it is equivalent.  Actually, doing  
> it ourselves has a lot of benefits.  The VM likes to cache urls in  
> a cache you can't flush, so redeploy tends to break.  Also File is  
> just easier to use than URL.
>
> -dain