Re: N-tier design

Thanks Jon.  That is some interesting input.  I must confess that I have not
done any socket programming, and so it did not readily come to mind.  If you
assume that the client can talk data queues (hmm, what could that be? :-D) are
there advantages/disadvantages to using sockets locally or remotely?

I take it that you agree with the concept; that is comforting.  Do you have any
pointers or resources that would be of benefit in implementing such an
architecture on the AS/400 (like somebody that has done it and wants to give
away the code)?

Ideally I would like to avoid writing my own application server of course.  That
is why CORBA, LDAP, or something similar would be of considerable interest,
remembering that I am not able to lock the host based version into a very recent
(modern) release though.  It appears to me that I am destined to write whatever
service abstraction layer I require.

More input?  Any nay sayers?

-Andrew Goodspeed
London Bridge Group
Norcross, GA  USA





Jon.Paris@halinfo.it on 03/21/2000 07:46:21 PM

Please respond to JAVA400-L@midrange.com

To:   JAVA400-L@midrange.com
cc:    (bcc: Andrew Goodspeed/Atlanta/LBSS)

Subject:  Re: N-tier design





 >> that seems to whittle it right down to data queues...... Am I way off on
this?  Who has two cents to add?

Any reason why sockets wasn't on the list?  Java does it real well and real easy
- It is on most any release of AS/400 you'd want to run on and can be accessed
directly from RPG if there are no C coders handy.

I would have thought that these days it was the natural choice.  Data Queues
force you to work with a client that can talk data queues - why restrict it like
that?



+---
| 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
+---