The diagram below shows more detail about the transcoding components that participate in request and response processing. This allows the transcoding proxy to be extended to support new data formats or to meet special transcoding needs. The WBI API is documented in the WBI Development Kit . The most common example is a generator that gets an object from a Web server. Editors can customize the response on its way back to the browser.
Monitors can do things like count accesses to particular pages.
The transcoding framework also allows industry-standard servlets to be incorporated as transcoders. Servlets written for other environments can be easily ported to run in the proxy, and new plug-ins written to the Java Servlet API will be usable in the many Web servers that support servlets. The transcoding proxy supports Version 2.1 of the Sun Java Servlet API . Servlets written to this API should run with few or no changes in the transcoding framework. The rules engine is the core of the WBI run-time services.