Actually, having come from a shop where we really do run our J2EE apps
in a distributed/clustered environment on mostly large IBM AIX and Z/OS
(mainframe) hardware/software, my suggestion was, at least partially, serious.
However, its up to you to decide at what point the cost of the
infrastructure is higher than what the application requires.
For example, in our shop, we use IBM's MQ-Series product heavily and
have a "middleware" team specifically for helping applications architect its
use as well as being responsible for its configuration and daily support.
This makes the use of things like MDBs a "no brainer" for async processing.
If you do not already have this type of support structure, it can be
very expensive to put one together for just one or two applications.
For applications where the vast majority of http requests require little
"clock on the wall" time, by doing work that takes long enough to warrant
a "busy" page on the servlet request threads risks a potentially
unintended "denial of service" attack on your server.
My own background is that of a mainframe assembly language programmer on a
team of people who supported a "home grown" TP monitor that is much like
and predates IBM's CICS product. By the way, this TP monitor is still in use
today and can still perform well on a machine that is running at 99% cpu busy.
I guess that makes me a bit sensitive to how the applications use/abuse
the supporting infrastructure. After having spent years preaching to
application programmers how queueing theory works and getting transaction
response times measured in the milliseconds, I still find it difficult to
imagine building an application where 10+ second response times are
"acceptable".
John Zerbe - Mellon Financial Corp.
Information Technology Solutions - Middleware Team
Phone: 412-234-1048 E-Mail:zerbe.jw@(protected)
AIM: 153-1315
-----Original Message-----
From: A mailing list for discussion about Sun Microsystem's Java Servlet
API Technology. [mailto:SERVLET-INTEREST@(protected)
Stølsvik
Sent: Tuesday, October 26, 2004 5:50 AM
To: SERVLET-INTEREST@(protected)
Subject: Re: (New subscriber) "Busy Page" - Aarrrrggggghhhhh.....
On Mon, 25 Oct 2004, Chris Ward wrote:
| > -Consider- using J2EE in -seriously- heavy-distributed
| > environments. Do not use even think about considering it to
| > show a "request being processed" page!!!!!
|
| Er... this has all gone a bit pear-shaped.
As a non-native English speaker, what would the pear-shape refer to?
I don't get that idiomatic expression at all...!
|
| I made the mistake of trying to round it off with a
| "funny" quip about having to use full-blown J2EE just
| to get a busy page.
I did get that, actually. The "hahaha!"-reply to your sole sentence was my
way of trying to convey that..! The "what ARE you saying?"-part of my mail
was directed to Zerbe's "Yup, J2EE's what you want, go on with the MBDs",
which I actually considered to be an actual serious suggestion. I might
have gotten that wrong, though..
Endre
___________________________________________________________________________
To unsubscribe, send email to listserv@(protected)
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
The information contained in this e-mail may be confidential and is intended solely for the use of the named addressee.
Access, copying or re-use of the e-mail or any information contained therein by any other person is not authorized.
If you are not the intended recipient please notify us immediately by returning the e-mail to the originator.(A)
___________________________________________________________________________
To unsubscribe, send email to listserv@(protected)
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
