I have started playing with iFolder on NW6.5.

My "problem", is object name collision. iFolder appears to use a
contextless login via LDAP. What happens when there are two objects with
the same name in subordinate OUs ? I've been trying to do some tests, but
not getting very far. (not sure if the name collision is causing the
problems, or my inexperiance with iFolder is to blame)

Getting round this with the WebAccess gateway wouldn't be too hard -
write some JavaScript to allow a user to select an OU or something. But
the Windows iFolder client isn't hackable.

How does iFolder handle name collisions ?

Are there any plans for future enhancements to iFolder to make things
easier ? (i.e. allow a user to select an OU) ?



Gordon Ross