On Thu, 20 Feb 2003, Charlie Brady wrote: >On Thu, 20 Feb 2003, Caskey Dickson wrote: >So for Courier compatibility bincimap should as well. >> >>point that you have to list "Foo (\NoSelect)". Still no >> >>recursion needed. >> > Recursion isn't *that* difficult. >> No, but it is slow requiring multiple opendir(3), readdir(3), closedir(3) >> calls, each with three stats, as opposed to a single set and a host of stat's. >True, but one doesn't very often build lists of deeply nested folders.
If we introduce folders within folders, we break Maildir++. And there's no reason that I can see, to have folders within folders. :/ >> Remeber IMAP requires that a >> minimum idle time of 30 minutes be supported, it is designed for online idle >> operation and if you have a mail server supporting hundreds or thousands of >> users, every system call is amplified many, many times. >Yes, that's true. Given that we are looking for scalability and >efficiency, will we also consider making use of kernel directory change >notification, if/when it is available? http://oss.sgi.com/projects/fam/ I've worked with selecting on F_NOTIFY and I've had very good experience with it. It's an existing functionality in Linux, but unfortunately it's not too portable. Currently, each Maildir or ++ subfolder is only stat'ed twice (one for cur and one for new) to check for changes, which is quite much faster than what some other Maildir servers do, but I'll take a look at FAM and see what it can do for Binc. Andy :-) -- Andreas Aardal Hanssen | http://www.andreas.hanssen.name/gpg Author of Binc IMAP | Nil desperandum
