Re: Namespace-based translator selection; project details

2008-06-22 Thread Sergiu Ivanov
Hello, On Thu, Jun 19, 2008 at 1:29 AM, <[EMAIL PROTECTED]> wrote: > On Wed, Jun 18, 2008 at 08:15:10PM +0300, Sergiu Ivanov wrote: > > On Mon, Jun 16, 2008 at 6:13 PM, <[EMAIL PROTECTED]> wrote: > > > > These could be put in a completely separate interface for translator > > > control. But it mi

Re: Namespace-based translator selection; project details

2008-06-18 Thread olafBuddenhagen
Hi, On Wed, Jun 18, 2008 at 08:15:10PM +0300, Sergiu Ivanov wrote: > On Mon, Jun 16, 2008 at 6:13 PM, <[EMAIL PROTECTED]> wrote: > > On Wed, Jun 11, 2008 at 09:01:27PM +0300, Sergiu Ivanov wrote: > > These could be put in a completely separate interface for translator > > control. But it might be

Re: Namespace-based translator selection; project details

2008-06-18 Thread Sergiu Ivanov
Hello, On Mon, Jun 16, 2008 at 6:13 PM, <[EMAIL PROTECTED]> wrote: > On Wed, Jun 11, 2008 at 09:01:27PM +0300, Sergiu Ivanov wrote: > > Frankly speaking, I still have no idea as to the communication between > > the proxy and the translators it loads. I suppose the proxy will have > > to exhibit a

Re: Namespace-based translator selection; project details

2008-06-17 Thread olafBuddenhagen
Hi, On Wed, Jun 11, 2008 at 09:01:27PM +0300, Sergiu Ivanov wrote: > On Tue, Jun 10, 2008 at 10:19 PM, <[EMAIL PROTECTED]> wrote: > Frankly speaking, I still have no idea as to the communication between > the proxy and the translators it loads. I suppose the proxy will have > to exhibit an interf

Re: Namespace-based translator selection; project details

2008-06-11 Thread Sergiu Ivanov
Hello, On Tue, Jun 10, 2008 at 10:19 PM, <[EMAIL PROTECTED]> wrote: > On Sat, Jun 07, 2008 at 11:21:10PM +0300, Sergiu Ivanov wrote: > > > Normal translators like "gunzip" would just use the underlying node > > > directly, forming an ordinary translator stack. Filter translators > > > on the othe

Re: Namespace-based translator selection; project details

2008-06-10 Thread olafBuddenhagen
Hi, On Sat, Jun 07, 2008 at 11:21:10PM +0300, Sergiu Ivanov wrote: > On Sat, Jun 7, 2008 at 3:13 PM, <[EMAIL PROTECTED]> wrote: > > Nevertheless, there is a lot of merit in your observation: I realise > > now that there is really no reason to externally classify the > > translators, and attach th

Re: Namespace-based translator selection; project details

2008-06-07 Thread Sergiu Ivanov
Hello, On Sat, Jun 7, 2008 at 3:13 PM, <[EMAIL PROTECTED]> wrote: > Note that the virtual nodes are always created on demand, the moment > they are accessed; so you would never actually create both variants up > front. But conceptually, you indeed could think of two virtual nodes > used alternati

Re: Namespace-based translator selection; project details

2008-06-07 Thread olafBuddenhagen
Hi, On Tue, Jun 03, 2008 at 07:50:14PM +0300, Sergiu Ivanov wrote: > On Tue, Jun 3, 2008 at 5:10 AM, <[EMAIL PROTECTED]> wrote: > > "-u" is more tricky that "-gunzip", as it doesn't skip one specific > > translator, but rather filters a whole class. While it is certainly > > possible to implement

Re: Namespace-based translator selection; project details

2008-06-03 Thread Sergiu Ivanov
Hello, On Tue, Jun 3, 2008 at 5:10 AM, <[EMAIL PROTECTED]> wrote: > "-u" is more tricky that "-gunzip", as it doesn't skip one specific > translator, but rather filters a whole class. While it is certainly > possible to implement this also by means of a generic filter translator > with some more

Re: Namespace-based translator selection; project details

2008-06-02 Thread olafBuddenhagen
Hi, On Fri, May 30, 2008 at 11:40:09PM +0300, Sergiu Ivanov wrote: > On Fri, May 30, 2008 at 6:32 AM, <[EMAIL PROTECTED]> wrote: > > > However, the matter about ignoring some translators ('-u', for > > > instance) is a bit foggy for me. Do you mean that these should > > > also be symbolic links?

Re: Namespace-based translator selection; project details

2008-05-30 Thread Sergiu Ivanov
Hello On Fri, May 30, 2008 at 6:32 AM, <[EMAIL PROTECTED]> wrote: > > However, the matter about ignoring some translators ('-u', for > > instance) is a bit foggy for me. Do you mean that these should also be > > symbolic links? > > That would be one of the implementation methods I suggested: Link

Re: Namespace-based translator selection; project details

2008-05-29 Thread olafBuddenhagen
Hi, On Tue, May 27, 2008 at 07:23:49PM +0300, Sergiu Ivanov wrote: > On Mon, May 26, 2008 at 8:49 PM, <[EMAIL PROTECTED]> wrote: > By the way, which would be the average size of a translator stack in > your opinion? I don't think my assessment of the situation is really > well-founded, by I suppo

Re: Namespace-based translator selection; project details

2008-05-27 Thread Sergiu Ivanov
Hello, On Mon, May 26, 2008 at 8:49 PM, <[EMAIL PROTECTED]> wrote: > As I already suggested, at least for the prototype, I believe it can be > implemented as a proxy which mirrors the underlying file system, and > does it's magic whenever a virtual file with the special suffix is > accessed. > >

Re: Namespace-based translator selection; project details

2008-05-26 Thread olafBuddenhagen
Hi, On Fri, May 23, 2008 at 06:50:47PM +0300, Sergiu Ivanov wrote: > On Fri, May 23, 2008 at 1:07 PM, <[EMAIL PROTECTED]> wrote: > The idea is much clearer for me now :-) As far as I can understand, > the namespace-based translator selection will _not_ modify the > filesystem permanently. Instead

Re: Namespace-based translator selection; project details

2008-05-23 Thread Sergiu Ivanov
Hello, On Fri, May 23, 2008 at 1:07 PM, <[EMAIL PROTECTED]> wrote: > > If the user tries to access 'file1,u' a second time, nothing will > > change, because a translator will have already been set on 'file1'. > > Stacking of translators should be done in an explicit form, like > > 'file1,u,x' (x

Re: Namespace-based translator selection; project details

2008-05-23 Thread olafBuddenhagen
Hi, On Tue, May 20, 2008 at 09:46:16PM +0300, Sergiu Ivanov wrote: > If the user tries to access 'file1,u' a second time, nothing will > change, because a translator will have already been set on 'file1'. > Stacking of translators should be done in an explicit form, like > 'file1,u,x' (x might me

Namespace-based translator selection; project details

2008-05-20 Thread Sergiu Ivanov
Hello, I've been thinking about my project recently and would like both to make my ideas known and to find out where they have weak points :-) I suggest creating a libnetfs-based translator which will be set on a directory and will allow the user to access files with special names like 'file1,u'.