Mailing List Archive: Arena workaround compromise?

Arena workaround compromise?

May 7, 1995, 10:28 AM

Post #1 of 5 (975 views)

I've thought about this a bit. While people who really want to experiment
with attributes in content-type returns *can* go through .asis or .cgi, it's
a kludge and they really shouldn't have to go through those kinds of hoops.
What I *really* don't want is for someone to ask "why did this break?", and
for me to have to tell them that we deliberately broke it in the 0.6.2 ->
0.6.3 transition.

However, if the code is #ifdef'ed, I can tell the guy instead to just compile
with -DW3O_SUCKS, or some such, until such time as the W3O sees fit to
release code which complies with their own standards. (Gee, do I sound
peeved?) So (he asks with trepidation), who has a problem with this?

rst

Re: Arena workaround compromise? [ In reply to ]

randy at zyzzyva

May 7, 1995, 7:43 AM

Post #2 of 5 (964 views)

Permalink

> I've thought about this a bit. While people who really want to experiment
> with attributes in content-type returns *can* go through .asis or .cgi, it's
> a kludge and they really shouldn't have to go through those kinds of hoops.
> What I *really* don't want is for someone to ask "why did this break?", and
> for me to have to tell them that we deliberately broke it in the 0.6.2 ->
> 0.6.3 transition.
>
> However, if the code is #ifdef'ed, I can tell the guy instead to just compile
> with -DW3O_SUCKS, or some such, until such time as the W3O sees fit to
> release code which complies with their own standards. (Gee, do I sound
> peeved?) So (he asks with trepidation), who has a problem with this?
>
> rst

I support this decision. +1 (BTW - Nice voting form RobH?)

I have to ask "does the W3O have Apache"? Should someone offer
Apache for a test server? (subtle hint) It would be hard to write
standard complient code without a server that behaves as such. I
would assume the the W3O is tuned in enough to be aware of these
things, but who knows...

Re: Arena workaround compromise? [ In reply to ]

fielding at avron

May 8, 1995, 1:35 AM

Post #3 of 5 (968 views)

Permalink

> I have to ask "does the W3O have Apache"? Should someone offer
> Apache for a test server? (subtle hint) It would be hard to write
> standard complient code without a server that behaves as such. I
> would assume the the W3O is tuned in enough to be aware of these
> things, but who knows...

As these things go, you may consider me to be an unofficial
"representative" of W3O (I'll be an official one for the summer,
starting June 1). Henrik is aware of the Apache stuff
(I showed it to him last month), but he is probably too busy
right now to look at things carefully. Most of the W3O team
know about Apache because I mention it (and rst) every time I
talk about content negotiation. However, since one of W3C's primary
goals is to maintain the CERN code, I doubt that they will be using
Apache as a primary server. I'll probably install it myself on
their test machines, assuming they ever catch that bloody cracker.

......Roy

Re: Arena workaround compromise? [ In reply to ]

brian at organic

May 8, 1995, 12:00 PM

Post #4 of 5 (962 views)

Permalink

On Sun, 7 May 1995, Robert S. Thau wrote:
> However, if the code is #ifdef'ed, I can tell the guy instead to just compile
> with -DW3O_SUCKS, or some such, until such time as the W3O sees fit to
> release code which complies with their own standards. (Gee, do I sound
> peeved?) So (he asks with trepidation), who has a problem with this?

+1, with it turned on by default (or strongly encouraged/documented).

Brian

--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
brian@organic.com brian@hyperreal.com http://www.[hyperreal,organic].com/