RE: Semantic content negotiation (was Re: expectations of vocabulary)

-- Golda

> Of course it can - 
> may be handled by a script handler, and it can make decisions 
> based on any environment variable, including browser version, 
> referring page, etc, what to return.
> Its not HTTP that is partitioning, but the intelligent server 
> process on the other side...

I never say it can.  In principle, you can do anything with HTTP.  For
instance, as I have given the example to put Xpath in the header too.  In
fact, you can do a lot of "cute" things with the HTTP protocols.  But what
you CAN do does not suggest that you SHOULD do. 

Use the right tool to do the right thing and carry it out at the right
places.  One of the primary principles in engineering is "separation of
concerns" because it helps the division of labor, which in turn improves

If you are talking a specific application logic, do whatever you feel
comfortable.  But if you are proposing an HTTP extension and standard
practice, you have to think much beyond if you CAN.



Received on Tuesday, 25 July 2006 22:28:55 UTC