Java Archi

[Mohit]

Out of these two architectures which one is more performance oriented and
why ??

1. Requests will be first gone to FrontController Servlet where authorization
and authentication is done and then request is passed to one another SERVLET
which will do business validations by calling EJB and forward the results
to final jsp page. Servlet name is taken out from XML file based upon the
URL type

2. Requests wiil be first gone to FrontController Servlet where authorization
and authentication is done and then request is passed to one another CLASS
which will do business validations by calling EJBs and forwarding the results
to jsp(View) . This class is initialized with Servletconfig and HttpRequest
request through reflection (Command Pattern). Class name is decided from
XML based upon the URL type.

[MarkN]

Depends on a few things. But I would venture a guess that #1 probably would
be faster. I would have to do some testing to be sure. But architectually,
#2 is better. And it could be coded to work almost as well as #1. I am
doing it like #2 and it is fast enough. I would rather have a flexible design
and lose a little on speed(if I even am).


Mark

"Mohit" <mohit_rathi@hotmail.com> wrote:
>
>Out of these two architectures which one is more performance oriented and
>why ??
>
>1. Requests will be first gone to FrontController Servlet where authorization
>and authentication is done and then request is passed to one another SERVLET
>which will do business validations by calling EJB and forward the results
>to final jsp page. Servlet name is taken out from XML file based upon the
>URL type
>
>2. Requests wiil be first gone to FrontController Servlet where authorization
>and authentication is done and then request is passed to one another CLASS
>which will do business validations by calling EJBs and forwarding the results
>to jsp(View) . This class is initialized with Servletconfig and HttpRequest
>request through reflection (Command Pattern). Class name is decided from
>XML based upon the URL type.