On July 4, 2002 at 08:53, Tobias Nijweide wrote:
earl(_at_)earlhood(_dot_)com said:
Allow folder specific component files to be located in a centralized
location. For example, if I wanted a custom "scan.monthly" format
file for my inbox, I would create a file with a pathname of `mhpath`/
scan.monthly.inbox. It does get ambiguous with sub-folders since '/'
cannot be a pathname (maybe tranlate '/' to '.').
Why not use a directory structure? By default we let the directory
structure correspond with your folders, but you can use an extra
step. So use ~/Mail/comps/company/replcomps for mail belonging to
folder ~/Mail/company/.
Sounds okay to me. I just threw out the idea to see what others
think.
- As soon as you do this you don't have automatic public folder
comps-file sharing anymore
I do not know if this is bad thing.
- This would work for other storage methods, although this wouldn't
store the files in your IMAP or whatever database yet. You could
easily build something for that if you wanted to.
I do not see a draw back here, with the exception that is you
take the folder abstraction approach, then how it is stored is
up to the implementation. Going down this train of thought further,
the per-folder component files could be stored in the folder directory
since it is an implementation detail. However, the directory
strcuture you mention is nicer since it protects from rmf and
easier management.
--ewh