In reference to Peter Lister's mail:
>Again, I don't know the code, and if Richard tells me that won't work
>in the current implementation or something very similar to it, I have
>to believe him. I simply comment that I can see no reason why it shouldn't.
I'm flattered with your confidence in me... Well, it can be done. The
reason I am somewhat against the upward and downward search is that
user's will not understand why they are receiving an error relating to
depth when they are not necessarily in control of who incorporated their
group. Even worse, one may not be able to figure out who has
incorporated a parent group because the "membership" listing may be
restricted to the owner of the group. I see the arbitrary restriction
as yet another source of confusion for errors. I agree that the nesting
of groups should be up to the administrator (which is why I made it a
command-line switch, but this might be argued that it might be better to
provide a pts interface and a flag in the database to ensure that all
the ptservers are consistent).
Someone else suggested that ACLs can be added to the ptserver. Well,
not without a fairly substantial rewrite and a database restructuring.
-Richard
