On Wed, Apr 17, 2002 at 09:52:38AM -0400, David Casti wrote: > My company has version 1 of our billing system written in PSP. We've had > some success with the product, and are in the process of finishing version > 2. The question is: Should we stick with PSP, or go to Servlets? A more > general question might be: What are the different circumstances to pick PSP > or Servlets?
> The key advantages of PSP for us is that we can have programmers and HTML > designers working on the same HTML files. The HTML guy does all the > markup, and the programmer comes through and inserts form controls, > includes banners, etc. Since the majority of the page is static HTML with > a few dynamically-generated controls, PSP seems to be the way to go. From > the examples, it looks like this would be difficult or impossible to do > with Servlets. There's also a third choice: Cheetah templates (www.cheetahtemplate.org). Cheetah was invented to do the text processing that's inconvenient to write directly into a servlet. You can do it two ways: either use the template itself as a servlet (inheriting from a class that contains your methods to generate the dynamic HTML) or write an ordinary servlet that instantiates a template for each large chunk of HTML it wants to write. The first way is closer to PSP and prob'ly what you'd want. Templates can inherit from templates, so the parent template can contain the HTML common to all child pages. (See the #block directive in the Cheetah Users' Guide.) -- -Mike (Iron) Orr, [EMAIL PROTECTED] (if mail problems: [EMAIL PROTECTED]) http://iron.cx/ English * Esperanto * Russkiy * Deutsch * Espan~ol _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
