This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
That, as so often is the case, depends on circumstances. Applications I work on tend to be for the intranet or extranet, where only registered users are allowed, and need to log in to access the application. Thus the application knows the roles a user is authorized for, and can show different -or additional- links and content, like administrative pages. If there's no concept of different user roles in the application it may make more sense to decouple the administrative site from the production site.
I'm fairly certain that sites like Amazon would have different servers -and different applications- for the admin stuff. No sense having that stuff on each server of your farm, when in reality only very few people would access it.
Suppose I went to use a single application for both, front-end and administration application. We decided to use WebWork for customers oriented application, and Seam for administration application. Is it advisable to use different frameworks for each application (regardless whether they are WebWork and Seam) ? Thanks.
Joined: Mar 22, 2005
Why would you want to use different, functionally overlapping, web frameworks within the same web app? I see no reason why it shouldn't work, but it seems an odd thing to do.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Administration concept for online applications