W3C home > Mailing lists > Public > www-webdav-dasl@w3.org > October to December 2002

RE: Proposed resolution for issue "score-pseudo-property"

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 28 Nov 2002 13:54:30 +0100
To: "Wallmer, Martin" <Martin.Wallmer@softwareag.com>, "'Julian Reschke'" <julian.reschke@gmx.de>, <www-webdav-dasl@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCGEDIFOAA.julian.reschke@gmx.de>

> From: www-webdav-dasl-request@w3.org
> [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Wallmer, Martin
> Sent: Thursday, November 28, 2002 10:42 AM
> To: 'Julian Reschke'; www-webdav-dasl@w3.org
> Subject: RE: Proposed resolution for issue "score-pseudo-property"
>
>
>
> Hi,
>
> does the score makes sense, when you cannot order by score? Why you don't
> want to have it as pseudo-property?

The problem with pseudo properties ist just that -- they are "pseudo"
properties -- basically a hacky workaround because somebody was too lazy to
define proper marshalling :-). Using pseudo properties not only opens a
whole set of new issues (what is if a "real" property by that name indeed
exists? What is the expected response for a PROPPATCH/PROPFIND response?),
it also requires lots of special cases in implementations (that need to
distinguish between real and faked properties). Things will even get worse
if different specs have *different* sets of pseudo-properties, thus
requiring each implementation to keep track in which context it was called.

Note that getting rid of this as pseudo-property does NOT mean that ordering
on score is impossible. It just means that the user agent will have to do
that. Note that this reduces both complexity in the server *and* potentially
moves CPU cycles to the client.

> ...

Julian
--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Thursday, 28 November 2002 07:55:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 March 2009 03:38:09 GMT