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

RE: A case for GETSRC (or other mechanism to that effect)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 4 Mar 2002 23:29:53 +0100
To: "CJ Holmes" <cholmes@4d.com>, "DAV" <w3c-dist-auth@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCKEGNECAA.julian.reschke@gmx.de>
> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of CJ Holmes
> Sent: Monday, March 04, 2002 11:11 PM
> To: DAV
> Subject: Re: A case for GETSRC (or other mechanism to that effect)
>
>
> >The source property is the only mechanism I know of that truly allows the
> >Web interface to be used for authoring of the source resources of
> >dynamically generated content.
>
> Agreed.  But this is irrelevant to most users.
>
> >Quite frankly, if a person cannot implement that in a trivial
> amount of time
> >then I'd like to know how their Web server manages to generate
> the dynamic
> >content in the first place.
>
> If it is so trivial, why isn't it implemented?  It's not because the
> programmers are simply lazy.  Look at all the stuff the *is*
> implemented wrt DAV.  Even fairly hard stuff like locks and storing
> arbitrary properties is implemented.  But this one trivial thing is
> not.  The *concept* is simple, yet it remains unimplemented after
> three years.

Because it's underspecified. There's even an entry related to this on the
RFC2518 open issues list.

> As long as people keep insisting that it is simple, I'm going to keep
> pointing that out.

So will I if this fact continues to be ignored.
Received on Monday, 4 March 2002 17:30:38 GMT

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