On Thu, Jan 03, 2002 at 10:51:15AM -0500, David Simcik wrote: > I am currently trying to piece together a personal site for myself using > Perl, MySQL, and Apache (alas, no mod_perl yet). I would like to seamlessly > deliver content to both HTML and WML browsers, perhaps even going as far as > deploying SOAP or XML-RPC as well (the difference, anyone?) for more > traditional fat clients I might have down the road. > > In essence, I am wondering what is the best model to emulate when I start > putting together these apps? I have heard that the XSLT/XML method using > [CGI] scripts to route requests, while much ballyhooed, can be a pain to > implement because of XSLT. I am also wondering how one can handle the myriad > of WAP/WML browsers out there, but perhaps that is a question for another > list. > > Any recommendations???
If you want to serve the same content for both HTML and WML browsers, look into the Template Toolkit (http://www.template-toolkit.org). You may also want to take a look at AxKit (http://www.axkit.org). As far as XML-RPC/SOAP, the easiest thing to do is to look into SOAP::Lite (http://www.soaplite.org). Note that the HTML/WML distinction is more about specifying multiple presentations for the same content, while adding SOAP/XML-RPC support is about publishing your website as an API. The best thing you can do here is to clearly separate the [business] logic of your website from the presentation. That way, you can plug those logic modules into SOAP::Lite handlers, and format them using Template Toolkit into HTML, WML, XHTML, low bandwith HTML, etc. HTH, Z. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
