So the usual IETF thought pattern around profiles is say we have might have profile A and B. Are their clients that want both? Are there reasons a server would only support one? How will this negation and if a server only does A and a client wants B, what will the interoperation be like? On 11/24/05 10:20 AM, "Geoffrey M Clemm" <geoffrey.clemm@us.ibm.com> wrote: > > I agree with this proposal. > > Cheers, > Geoff > > Julian wrote on 11/24/2005 08:31:14 AM: > >> > So what I would propose is to >> > >> > a) agree on a certain set of server features that those clients expect >> > (strong ETag on PUT, octet-for-octet identity of representations, ...), >> then >> > >> > b) define a profile for WebDAV that covers this, and a simple way for >> > clients to discover whether any given resource supports this. >> > >> > IMHO this definition should go into a separate document. This will also >> > reduce the amount of open issues on RFC2518bis for now. > >
Received on Thursday, 24 November 2005 20:41:01 UTC