Method and Apparatus to translate/transcode marked-up text in a real time fashion
Original Publication Date: 2001-Apr-22
Included in the Prior Art Database: 2003-Jun-20
Transcoding without a proxy The essence of this disclosure is an alternative to proxy servers that, for transcoding, gives control to the application running in a browser, rather than the network itself. Traditionally, proxies are servers, or programs, placed in the middle of a network connection unbeknownst to the client and the server. Specifically, in Internet transactions, the browser requests something from a web server. In the middle somewhere, there might be a proxy server to do something, such as route the request through a firewall for security, or in other cases, to process the returned markup after it comes in from the server, but before it gets to the browser. Often times browsers are configured to go through proxy servers or processes, most often for security and firewall access. Other proxies are put in place and are totally invisible to the client or server. Such a case is with a transcoding proxy. Transcoding, (the term used for the technology to take one tag format (such as HTML) and convert it to another (such as WML) to enable the presentation of HTML data on WML devices, in this example) is done through proxy servers. The problem with this approach is that it is totally out of the control of the browser, or the application/web site being accessed. The alternative disclosed here is that rather than put an “invisible” proxy server in place, this could be accomplished under the control of the application or web site itself through the use of web server-side programming. The example here will use Java servlets, but this could be anything from Java, to ASP, to CGI and most any other web server side programming model.