Re: [eGroupWare-developers] Another round of filemanager

[Stefano S. <ste...@cb...>]

> Lets also spend a column options. some backends might need to have
> options.
> e.g. if a ftp is reached just by one ftp-user
> /ftpdir 	egw.ftp....	username=...,password=xyz,mask=755

Ok, this make sense.

> I think it's better to let every stram manage its own acl's.
> Think of a samba backend. The rights definitly have to come from the
> sambaserver.
> or think of the ftp-backend obove, the rights come from the option.

I agree but AFAIK I can not set access mode using streams since chmod function 
works only on local filesystem, so the user can not set the permissions of 
files stored on remote locations (e.g. If I link a file stored in my home 
which is a samba share I need to make it readable by other users). A solution 
is that every resource should be configured to be fully accessible by the web 
server, than vfs layer filters user's requests (and set correct permissions 
on this).

> ack. There a a lot of functions dealing with metadatas in the stream
> interface. maybe we have to do some reseach and find witch of them we
> want to use.

If have found only stream_get_meta_data, do you know more about this ?

> well, in a normal filesystem a symlink also breaks if you move the
> file. But anyhow, it's a nice feature if the vfs class hooks into the
> links and changes the corresponding links.
> To store the url (or lets call it vfs_path) is a good idea.

Indeed, probably it is better if for the first step we don't worry about 
broken links.


Bye, Stefano