- From: Miles Thompson <miles@mail.com>
- Date: Tue, 12 Jan 1999 09:36:17 +1300
- To: w3c-dist-auth@w3.org
Lisa,
>It might be a good idea to make these properties a "bundle" -- if one is
>supported, all should be supported. That would make it easier for the
>client to figure out what to expect.
If I were writing a client would it be reasonable for me to expect that
such properties as for example a collections 'childcount' are available
in any "WebDav compliant" server ? If not then the stating of their
'optional' existance only causes confusion for me as a developer.
Surely the whole purpose of a standard is that the whole thing,
*all* the properties and methods, API etc can be treated as a 'bundle'
that I can assume to exist. If I cannot assume some properties exist
then I would have to, as you say, fall back on more primitive methods,
in which case why even put them in the spec?
_
o | |
_ _ | | _ ,
/|/ |/ | | |/ |/ / \_
| | |_/|_/|__/|__/ \/
miles@mail.com
miles@helios.co.nz
Received on Monday, 11 January 1999 15:39:27 UTC