From: Frank L. <fra...@go...> - 2009-12-29 13:00:21
|
2009/12/29 Anton Starikov <ant...@gm...>: > My symlinks work is in progress and almost ready, ... Great! >... but I have another question. > I checked how noadouble option works. It is a bit far from ideal. > Without noadouble afpd creates resource forks all the time on first access to file, even for read only. I guess this is not really itching you, but it disturbs me a little bit. You mean eg enumerating a directory on a options:ro volume creates adouble files? Afaict that would be the way we designed it in two ways: - afair we removed the not long ago introduced bevaviour of creating adouble files on dir enumeration - on options:ro volumes we shouldn't be creating anything > Which I thought could be avoided by noadouble. But when noadouble is active then resource fork will be not > created even if client really wants to store something (like attributes by SetFile). Which isn't ideal also. > > I think it might be good idea to introduce an option when resource forks are created only when clients explicitly ask > to store in resource fork something which is differ from default contents of fork. Well, I dont really care for noadouble, because as said it is broken by design, but in other ways then this. The desired behaviour you describe should in fact be the current behaviour. Ie on file/dir creation dont create adouble file (broken by design: creation time is lost), only create it if necessary to store eg. ressource fork of FinderInfo stuff. |