Thanks for the links. Just breezing through it, I see that it's pretty well just re-using the Servlet type interface. Since the Python is being compiled down to JVM ByteCode, it's not surprising that the compiled Jython code can interface with the Servlet engine.
Though the criticism of JSP is somewhat valid, I don't think a Servlet approach necessarily gets the seperation of Content from Presentation that is being sought. It shifts the onus from the presentation layer, back to the content layer. That is, instead of having business rules scattered throughout the html like yo have with JSP, you have the problem of html scattered throughout the Model layer of the Servlet.
Ideally, most JSP applications are in reality a combination of JSP, Servlets, and business objects. The JSP should have very little programming logic other than providing a template for the objects. Of course, theory and practice are not the same in many, if not most, instances.
|