Hello,
I welcome any opinions on whether the following small project
sounds like a suitable pilot EJB project:
I have an applet that currently uses cgi to connect to a legacy
graphing application on a web server. The graphing application
queries a database and produces line graphs as pdf files.
My project is to replace the legacy graphing app with an N tiered
graphing app. I had initially planned to use servlets to read data via
JDBC and return the time series data to the applet, which would build
the graph objects using a third party tool. The app is not really
transactional
in nature, I am interested in evaluating EJB technology with a project
where there is some pay-off.
Is there any gain in using entity EJBs to read data from a database?
The database stores a historical set of data points and is written to on
a daily basis. A typical graph would involve reading say eight curves
each with 2000 points. There will be perhaps 30 concurrent users.
Would EJB make it any easier to cache commonly used data?
Any opinions welcome.
Peter Booth
[EMAIL PROTECTED]
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
