Additional work needed
Some adaptation of Cocoon is required though:
support for sessions needs to be in the engine
browser capabilities database to be able generate the presentation with the best user experience
generate the MIME type expected by the browser, even if the browser type is not specified in the capabilities database
design the XHTML language and implement the XSLT sheets
post-processing of generated pages to split large pages in smaller ones that fit on the device
Notes:
- Session support is very important in designing and implementing Web applications
- Cocoon doesn’t take into consideration the Accept: HTTP header to determine MIME type the requesting browser accepts. Thus if the WAP device is not listed as a WAP device in Cocoon’s configuration files, Cocoon will assume it’s an HTML browser and send back HTML pages. The modification makes Cocoon behave in the correct way, even when the browser isn’t listed in the configuration file.
- Post-processing is not yet implemented
- All the changes to Cocoon mentioned above were posted on the Cocoon mailing list and appear in the “Patch Queue“ page at Cocoon’s Web site. The XHTML language and XSLT stylesheets are not yet posted.