[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Fwd: UFN paths given in a browser type environment.]

All,

  I am forwarding this on from the IETF working group discussion
that is related to LDAP and DN server platforms.  I felt that
the first part of Scotts concerns have relevance to the discussion
in part to This list.  Please comment.

Regards,
-- 
Jeffrey A. Williams
DIR. Internet Network Eng/SR. Java Development Eng.
Information Eng. Group. 
Phone :972-447-1878
E-Mail jwkckid1@ix.netcom.com


I have a concern that an LDAP path given in a browser environment will
be of the form:
	ldap://dns/name1/name2

This will be great as far as the user is concerned.  The problem is that
currently the clients are required to find each component of the path in
order to build the DN.  

If a directory server on the internet is getting millions of hits a day
from different users, the amount of traffic to the server will be
increased alot simply by the clients (browsers) being required to break
down each component of the path and verifying with the server that it
exists, and in the process building the DN from the responses.

If this is the case, users will see a long delay if the amount of
traffic the server handles is high, or the server location is a long
distance from the user.

If this perceived problem exists then the it could be eliminated by the
server parsing the slash path instead of the client/browser.

The best news would be that I'm incorrect or the possible problem I
perceive has been handled.  Please let me know in either case.

Thanks,
Scott