Re: jsp sharing problem

From:

=?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk>

Newsgroups:

comp.lang.java.programmer

Date:

Mon, 12 May 2008 18:26:41 -0400

Message-ID:

<4828c41a$0$90269$14726298@news.sunsite.dk>

Daniel Pitts wrote:

Arne VajhHj wrote:

Daniel Pitts wrote:

The other thing you can do is externalize the lucene index, possibly
via solr, which is a web-service shell that uses lucene to manage
document search.

---(HTTP)---JSP---(HTTP)---web service

looks like a classic anti-pattern ...

Actually, a flow like this looks pretty reasonable to me.

  User Request Servlet Controller Data Access Web Service
    --+-----(http)----->| | | |
      | |-(Method)->| | |
      | | |---(Method)-->| |
      | | | |-----(http)->|
      | | | |<------------|
      | | |<-------------| |
      | | |--(jsp)->View | |
  <---------------------------------------------/ | |

It's called multi layered architecture, and the underlying protocols
(http vs method, etc...) are irrelevant, or at the very most minor
implementation details.

I do not have a problem with the multi-layered design for this.

I have a problem with the multi-tiered design for this.

Using HTTP instead of in-JVM calls or even a binary protocol has
a huge impact on performance.

And it is a classic anti-pattern.

If you happen to own or have access to Fowler "Patterns of
Enterprise Application Architecture", then check chapter 7.

Arne