W3C home > Mailing lists > Public > public-bpwg-ct@w3.org > October 2008

Re: Web browsers, HTTP and transcoding

From: Tom Hume <Tom.Hume@futureplatforms.com>
Date: Fri, 17 Oct 2008 00:02:35 +0100
Cc: public-bpwg-ct <public-bpwg-ct@w3.org>
Message-Id: <68E9BB4B-F90C-4D0A-859B-D5EBC6102D71@futureplatforms.com>
To: Rotan Hanrahan <Rotan.Hanrahan@MobileAware.com>
Does this imply that transcoding proxies shouldn't transcode items of  
content with MIME types that is "text/xml, application/xml or ends in  
+xml (ignoring any parameters)" (the ones referred to in the XHR  
standard)?

On 16 Oct 2008, at 23:51, Rotan Hanrahan wrote:

> In these scenarios, mobile Ajax should stick to raw text, XML or  
> JSON as a payload format. If it is communicating with fragments of  
> HTML and you've already adapted (or otherwise "enhanced") the page  
> in which the Ajax is operating, the chances of that fragment of HTML  
> being of any use any more (adapted or not) are significantly  
> diminished already.
>
> Good point about the UA though. I must double-check.

--
Future Platforms Ltd
e: Tom.Hume@futureplatforms.com
t: +44 (0) 1273 819038
m: +44 (0) 7971 781422
company: www.futureplatforms.com
personal: tomhume.org
Received on Thursday, 16 October 2008 23:16:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 16 October 2008 23:16:30 GMT