|
This sounds interesting. I'm just starting to try this sort of thing, and I find two tiers a lot easier to manage, particularly using record level I/O. I'm not convinced that's the right thing to do, but it's easier. I think it's great to have some discussion, particularly from people with more experience. > -----Original Message----- > From: Smith, Nelson [mailto:NSmith@lincare.com] > Sent: Wednesday, April 10, 2002 11:01 AM > To: 'rpg400-l@midrange.com' > Subject: RE: Separation of Presentation, BL, and I/O Tiers > > > I'll check out the article and would love to see examples. > > When you say mediator, do you mean something like converting > the application > over from one that uses a entire externally defined record to > one that uses > only the data it really needs, through a GetCustName() and > GetCustCity() > kind of procedure, for example? Then, the procedures would > be the only ones > actually using the I/O modules? > > I've implemented this in a few file-specific service programs > where the > actual I/O module is a local procedure in the service program and the > exported procedures use it, but haven't gotten real far with > that method > yet. The lack of generic-ness has been somewhat of a stumbling block. > Isn't this what the Get and Set methods in OO programs are > all about? I > think I've read they do a Get/Set pair for every field in a file. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.