Maybe it’s an idea to handle parts of this problem with (php5)
exceptions. Buildin streams will also throw exeptions if something
with native acl goes wrong.
Probably it’s me, but the problem is a bit difficult.
We can summarize the communication process as:
eGW <-----------> streams <------------> resources
where “resources” can be the physical file or everything managed by the
stream.
Beetwen eGW and the stream we have eGW ACL, beetwen streams and resources we
have the specific ACL of the stream (e.g. ftp user, accounts on the
system, …): mapping this two identities is not so easy.
Let’s analize some case:
“custom streams” : we can insert ACL management in stream itself, no problem
here (besides actually writing the code).
“built-in streams that require remote authentication” (ftp, svn, samba,
…):
they can be handled defining a user fstab with personal credential that we
pass to the stream. This works but we must think of a system for supporting
functions like “chmod”.
“built-in streams that require local authentication” (only file): they must
be
handled in a different way, probably it’s better to not handle this at all
and wrapping the access to file-system with a custom stream (egwfile ?).
any other example? considerations?
Bye, Stefano
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net’s Techsay panel and you’ll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers