W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2000

Re: Should I use displayname?

From: <ccjason@us.ibm.com>
Date: Wed, 19 Jan 2000 13:04:41 -0500
To: "Rickard Falk" <rickard.falk@excosoft.se>
cc: w3c-dist-auth@w3.org
Message-ID: <8525686B.0063603F.00@D51MTA03.pok.ibm.com>

>>
When I'm trying to perform a directory browsing, that I'm going to present
to a user. Should I then present the Displayname info or should I pars the
href to get the name of the resource, from the Propfind request?
If I should use the Displayname info, can I rely on that it only contains
the name of the resource and not the complete path? ( this seems to be the
case for IIS, Xythos, Zope. But not for CyberTeams server )
>>
Noone has answered, so I will take a stab.

I don't think you can count on it containing anything and even that it
exists.  If it does exist, it does seem like the thing you'd want to
display.

Note: I don't think it's even technically required to correspond to
the URI at all.

Note: in the presence of multiple bindings, if the server initializes it
to the URI and treats it as a dead property, that URI might be different
from the URI from which it was accessed.  This unexpected behavior is even
possible (but less likely) if the value is only initialized to the last
segment of the URI.

That's only the technical answer.  If you were asking for a consensus
answer, you can add DAV4J to the list.  It currently treats it as a dead
property that gets initialized to the full URI.  It also allows the client
to change the displayname to anything they wish.
Received on Wednesday, 19 January 2000 14:09:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:53 GMT