RE: Java and CPU

Again, I concur, Larry, with your sage remarks <smile>.  For most of my
development, I use both a thick client and a thin client interface; by using
the thick client I can debug everything quite easily on my PC.  I'm slightly
ashamed that I've yet to learn how to debug servlets directly in Visual Age;
in fact, I'm not even up to 35 of VAJ yet, but I will be as soon as the new
AS/400 comes in next week.

As to the encapsulation of database I/O, I highhly recommend a level of
object abstraction so that you can easily plug in native DB2 access (I use
message-based calls to a server) as opposed to SQL.  As I've pointed out,
native DB2 is much faster than SQL for many things, and it's generally a
good idea to allow either.  Heck, it's generally a good idea to separate
your business object and data source design anyway - this is the first step
towards the componentization  required for EJB, anyway.

Joe

> -----Original Message-----
> [mailto:owner-java400-l@midrange.com]On Behalf Of Larry Loen
> Sent: Friday, March 02, 2001 3:31 PM

> With only a bit of work and imagination, one should be able to do
> most of one's debug on the client machine with an IDE; I do little
> formal debug on the '400 myself and yet deploy to the '400 proper.
>
> One key trick:  Encapsulate, with a simple object hierarchy, the
> distinction between using the Toolbox driver and the Native driver.
> This lets you use the toolbox for remote (PC and IDE access) of
> the DB and the faster native access when you deploy for real.

+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---