Subject: Re: [netatalk-admins] enumaration optimization/trash can problem...
From: Harry Zink (mail-atalk@fizbin.com)
Date: Sun Mar 29 1998 - 03:46:42 EST
>In fact I was thinking about caching type/creator/comment/icon/other
>miscellaneous information with the data the catalogueing daemon proposed
>by Adrian would collect.
This should be very possible by caching the relevant information, and
before verifying against something like a checksum before reading from
the cache (to make sure the data is current, and/or hasn't changed - if
it changed, update the cache...)
We've used this in the case of certain directory cacheing mechanisms, so
I do not think it would be that impossible to implement.
What worries me on a different level is the 'trash can' problem, which
could be a permissions issue, but could probably be very easily resolved
by s a slight change in the code.
Instead of creating 'trash folder #xx', why not just create folders
labeled 'trash can folder_username_xx'?
That way, each logged in user definitely creates and gets a unique trash
can assigned to them. The only problem I see is when you have a user
logged in multiple times (a possible situation), and you end up with
multiple trashcans for the same user... this could lead to deletion
nightmares.
Of course, this could be eliminated by eliminating the # at the end, and
only extending the traschcan folder name by the 'username' - then every
subsequent login under the same name would inidicate the current status
of the trash can for that particular user...
Do-able???
Harry
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:32:01 EST