Design of first distributed architecture
Okay, so I'm trying to design and implement my first distributed project, and I want to make sure my general design is okay before I start. Like I say, I've never used J2EE before, and I'm still learning about it. This is very general.
Problem: Design a login system complete with the following aspects:
- Abasic login window/applet that takes a username and password and verifies them. If they are valid (as determined by specific business logic), return a cookie (assume they are allowed for now) and allow the user access to the requested resources on the server. (Note: I think I'm using the term business logic correctly, but tell me if I'm not.)
- Abasic registration window/applet that takes a user's information. Depending on the business logic, the user will be registered to the database for a certain access level or will become a 損ending user,?which will be reviewed by an administrator before being allowed to access the server抯 resources.
- Anadministrator抯 window/applet that is basically a view of all that goes on in the server. This includes
* current users
* pending users
* audits
* files on the server
* any directory and access protocols
* server settings
Proposal: I plan to follow basic J2EE architecture patterns: The browser will allow access to all of the windows. The windows will call on servlets, which will call on EJBs to access the appropriate tables, all in the same database. I will make a servlet for each table category: UserServlet (for accessing the user list, maybe the list of pending users), AuditServlet, SettingsServlet, LdapServlet, etc.
Should I make a separate servlet and EJB for each category (as listed above)? I still have to read up on EJBs before I implement this.
So that is my basic skeleton, but I have no idea as to its quality. What do you think?
theAmerican
