> It gets quite complicated, because for the same URL the client might request > a Japanese, shift_jis, text/html view, while another might request a simple > image/jpeg...
> It basically implies that the URL is a resource _for_real_ and that the Resource -> 'semantics' or 'the bit of info'. > client can decide the way in which he wants to receive it.. Yes, i.e. which 'rendition'. But it gets worse.. (or more complex).. some browsers say that they are fine with */*; i.e. just everything, which in actually practice makes a real live implementation a bit more complex than needed. > But there is a problem... Proxies and caches... .. > jp and one using Linux in en_US, if the first guy requests > "http://www.vnunet.com/";, I'll deliver the page the first time in jp, > encoded in shift_jis (let's not track content-type for a sec). .. > it hits, so, to both of them, I'll end up serving the same Japanese > shift_jis content... .. > Not good... Needs more thinking indeed... Correct; this is (or was) a common issue with proxies. Most proxies and caches now get this right. Dw
