- From: Robert Finean <Rob.Finean@openwave.com>
- Date: Wed, 23 Jul 2008 21:45:14 +0100
- To: "public-bpwg-ct" <public-bpwg-ct@w3.org>
Here's my contribution for appendix B.5: ---- 1. The user requests resource P on website S. 2. The CT-proxy intercepts the request and requests resource P with original headers. 3. The server returns a HTTP Status 200 OK and content designed for a specific browser, as that is what resource P specifically is. However, in the HTML mark-up the server includes a <link type="alternate" media="handheld" href="Q" /> to indicate that it has equivalent content in different formats at different URIs. 4. If Q is equal to P this confirms that the content is the handheld version of a range of available formats and the CT-proxy parses the response, may apply transformation if needed and possible, and forwards the response to the user. 4. If Q does not equal P, the CT-proxy recognises that the alternate handheld format is more suitable for the user and makes a request for resource Q, still using original headers. 5. The server returns a HTTP Status 200 OK and content designed for a handheld browser. 6. The CT-proxy parses the response, may apply transformation if needed and possible, and forwards the response to the user. ---- Thanks, Rob -- OPENWAVE Dr Robert Finean OpenWeb Product Manager
Received on Wednesday, 23 July 2008 20:46:24 UTC