On Fri, 2010-10-15 at 08:43 -0700, Costin Manolache wrote:
> But I hope you agree you were right, at least in the long term :-)
Who cares about the long term, nobody uses 10 years old code. Oh,
wait ;)
Rémy
-
To unsubscribe, e
On Fri, Oct 15, 2010 at 8:13 AM, Remy Maucherat wrote:
> On Fri, 2010-10-15 at 07:57 -0700, Costin Manolache wrote:
> > I remember many years back I was arguing in favor of DirContext - pro
> > arguments were
> > "it's a standard", bundled in JDK, probably more target implementations
> will
> > b
On Fri, Oct 15, 2010 at 8:24 AM, Mladen Turk wrote:
> On 10/15/2010 04:57 PM, Costin Manolache wrote:
>
>> Are you going to replace DirContext ?
>>
>> If yes - great, but please first send a quick summary comparing your API
>> with the other VFS
>> around in apache. I think commons has few target
On 10/15/2010 04:57 PM, Costin Manolache wrote:
Are you going to replace DirContext ?
If yes - great, but please first send a quick summary comparing your API
with the other VFS
around in apache. I think commons has few targets, including a hdfs, I
remember there are more.
Well it's not a VFS
On Fri, 2010-10-15 at 07:57 -0700, Costin Manolache wrote:
> I remember many years back I was arguing in favor of DirContext - pro
> arguments were
> "it's a standard", bundled in JDK, probably more target implementations will
> be available, etc.
> I think Remy was arguing that it's too complex an
Are you going to replace DirContext ?
If yes - great, but please first send a quick summary comparing your API
with the other VFS
around in apache. I think commons has few targets, including a hdfs, I
remember there are more.
If no - not sure what's the point of replacing java.io impl, I assume y
I remembered Mladen and VFS discussion, elsewhere.
Google confirmed it to me :
http://www.mail-archive.com/commons-...@jakarta.apache.org/msg82888.html
Your code is still http://apvfs.sourceforge.net/ ?
-
To unsubscribe, e-mail
2010/10/15 Mladen Turk :
> Hi,
>
>
> I'm working for quite some time on the light-weight
> VFS layer (with the java.io.* as the only provider at
> the moment) to be used as the Tomcat's physical file
> system access. The ultimate goal is to be able to run
> the Tomcat on top of things like Hadoop o
On 10/15/2010 09:58 AM, Mark Thomas wrote:
On 15/10/2010 08:02, Mladen Turk wrote:
Hi,
I'm working for quite some time on the light-weight
VFS layer (with the java.io.* as the only provider at
the moment) to be used as the Tomcat's physical file
system access. The ultimate goal is to be able to
On 15/10/2010 08:02, Mladen Turk wrote:
> Hi,
>
> I'm working for quite some time on the light-weight
> VFS layer (with the java.io.* as the only provider at
> the moment) to be used as the Tomcat's physical file
> system access. The ultimate goal is to be able to run
> the Tomcat on top of things
Hi,
I'm working for quite some time on the light-weight
VFS layer (with the java.io.* as the only provider at
the moment) to be used as the Tomcat's physical file
system access. The ultimate goal is to be able to run
the Tomcat on top of things like Hadoop or similar distributed
file systems (eg
11 matches
Mail list logo