当前位置:首页 » 软件开发
开发技术指南» 文章正文
    引言: There are myriad approaches to
 

 

 ·webtop architectures for j2ee @ jdj    »显示摘要«
    摘要: in the early 90s, many companies invested in traditional client/server architectures by building fat-client applications with rich graphics that offloaded legacy-system processing time. gui busi......
    摘要: there is a raging debate in the developer community: microsofts new platform .net versus the sun standard j2ee. j2ee has been around for a few years, while microsofts attempt is decidedly the new ki......


Alternative Approaches to Architecting Logon and User Management @ JDJ

there are myriad approaches to architecting logon and user management in the j2ee environment. this article addresses some alternative j2ee architectures as well as the strategy used by each alternative and the code for implementing each solution. ill focus on the end user - not the business purpose of many of todays medium- to large-scale web apps - but my primary focus will be on state-of-the-art solutions.

first, some background information on struts and mvc frameworks: struts is on its way to becoming a de facto standard for developing medium- to large-scale web-based applications on the java platform. struts fits nicely into the j2ee technology stack by filling some gaps not addressed by the servlet/jsp standard or the ejb standard. a framework can isolate the developer from the ever-changing j2ee apis and make it easier to get j2ee applications completed in a shorter time frame. (although, caveat emptor, struts is an ever-changing api.) a framework does this by taking care of the low-level plumbing and difficult programmatic challenges involved with building a j2ee application. basically, a good framework will do the dirty work for you. for more details, see the references section at the end of this article.

lets begin with the end user at the client in figure 1 or 2 and work our way toward the server shown in bold outline at the right side of these figures. figure 1 shows a filters-based design. filters sit between the end client and the requested resource and are able to intercept the request before the resource sees it. figure 2 shows another design where front-end processing is incorporated into the application; in the latter case, changes to one component mean changes to the application proper. struts apps can be built either way.

filter strategies

before launching into filter strategies, heres a brief introduction to filters - a feature introduced in the servlet 2.3 api. the contents of the filter are written in java and are thereby flexible and easy to maintain without touching the application code. as shown in figure 1, filters can be chained and ar
...   下一页
    摘要: a major roadblock to using any of the server-side scripting architectures for developing commercial software is the fact that (traditionally) the source code must be delivered to customers when depl......
» 本期热门文章:

©2000-2007 All Rights Reserved. 最佳浏览:1024X768 MSIE