Please tell me if this makes sense to you For an application the following are allowed actions: Log in Manage Account View Transactions List Submit Transaction Log out
As I have mentioned in the other thread the actions (not all) are executable from browser or an application. For browser the session is kept with the use of cookies or URL rewriting. For an application I will return a token upon Log In request and that token will be used in subsequent requests by that application. The requests from browser will build beans that will be read by JSP pages and the application requests will return XML responses. Not all actions are allowed by either interface. Account can be managed through the browser but only an application can submit a transaction. Otherwise Authentication uses the same source and other services are shared (account database for example). Questions: 1. How much separation do the two interfaces need? The application interface needs to have higher availability than the browser interface but they're VERY similar in processing requests. For example the authentication request is handled basically the same way but instead of creating an AuthBean to be set in a session the application will get an XML message. Should I create base AuthenticationHandler and then inherit for other response types? 3. Do you have any other comments on this? Are there any ready made patterns that do this? It is possible that the application interface will have to be able to return other formats too (other than XML). Thanks, d. -- David Mossakowski [EMAIL PROTECTED] Instinet Corporation 212.310.7275 ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
