"Cary O'Brien" wrote If I understand it correctly, your phone sends out a request which is turned into a http request by the cell phone company. The site then returns wml (an xml doctype), not html, which deals with things like what the buttons do, as well as encoding whatever content you can fit on the tiny screen. So all a zope site would have to do is add a new mime type (not sure what it is), and serve up the wml rather than html.
Using zope DTML and regular zope stuff to handle common menus and control of pages should all fall together.
The only things that would have to be changed (and I don't know how to do this) are:
1) mime type 2) file suffix (.wml instead of .html)
You'd also have to produce the files in WML rather than HTML. The way I was thinking about it was to have two sets of template pages - one produces HTML, the other WML. The alternative is to have one set that produce XML, and convert them on the way out of the system. You'd probably also have to restructure your web applications to better suite the WML model. The other thing you need is a phone company willing to let you supply them WML so that they can send it to the phones (there's WAP-over-SMS, but I don't want to think about how slow and expensive that would be). -- Anthony Baxter <anthony@interlink.com.au> It's never too late to have a happy childhood.