Hi Jarek, As you probably have noticed, directory tree design requires consideration of many factors as well as foresight :]
My strategy when acting as a directory architect has been to first structure the data in the most natural and real-world-reflecting way, and then make adjustments where necessary, e.g. to speed up retrieval, or ease management or to allow for possible changes/renaming. Judging by your post, it looks like the primary purpose of your directory is to map the domains and their respective users, not to store information about the actual users (what general purpose directories do). My rule of thumb is to apply group memberships in situations when these are volatile and subject to frequent change; and use tree-encoded structure to store "belong-to" relationships that are relatively solid and unlikely to change. Greetings, Vladimir -- Vladimir Dzhuvinov :: software.dzhuvinov.com
