JSP Technology -- Friend or Foe?
By
Brett McLaughlin
2003-03-07
Designer vs. developer
A final (and admirable) goal of JSP technology worth mentioning is that it seeks to establish clearly defined roles in the application development process. By ostensibly breaking content from presentation, JSP technology creates a clearer distinction between the designer and developer. The designer creates markup, using only standard HTML, WML, or whatever language is appropriate, and the developer writes code. Of course, many designers today have learned JavaScript, so it should come as no surprise that many of these same designers have begun to learn JSP coding. Often, instead of just doing pure markup, they encode a complete JSP page and hand it over to the developer. Then the usual tweaking takes place, and the developer puts the JSP page into place as a front-end for some portion of the overall application. The key, though, is that many designers do
not learn JSP coding, so it must also be workable in that environment.
First published by IBM developerWorks
|
|
|
3 Votes |
|
|
|
|
You might also want to check these out:
|
Leave a Comment on "JSP Technology -- Friend or Foe?"
You must be
logged in to post a comment.
Link to This Tutorial Page!
