Re: DAV and DeltaV properties for an activity
Werner Donné <[email protected]> Mon, 29 May 2006 18:10:41 +0200
| Newsgroups | gmane.ietf.deltav |
|---|---|
| Organization | Re BVBA |
| Message-ID | <[email protected]> |
An activity has no contents, so the HTTP headers wouldn't apply and hence the corresponding properties have no meaning either. Werner. Julian Reschke wrote: > Werner Donn=E9 schrieb: >> Hi, >> >> Section A.13 of RFC 3253 says that an activity supports all DeltaV- >> compliant properties, which include the DAV properties. What would >> be the meaning, for an activity, of the properties getcontentlanguage >> and getcontenttype? Section 3.1.4 seems to allow to leave them out >> of the supported-live-property-set if they have no semantics for an >> activity, but shouldn't the semantics be explained for the common >> live properties if there are any? >=20 > Well, the semantics are the ones defined in RFC2518. That is, if an > activity responds to a GET request, then those properties should behave > just as the HTTP response headers Content-Language and Content-Type. >=20 > What am I missing? >=20 > Best regards, Julian >=20 >=20 --=20 Werner Donn=E9 -- Re Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: [email protected]