The error handling business is what could most influence the business logic design, but I agree that it's the communications interface that needs to map whatever is used in the BL to what's used in the transport.
Eric
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of matt.haas@xxxxxxxxxxx
Sent: Thursday, October 04, 2007 3:54 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: Business Logic Servers ( was: MVC in RPG?)
<snip>
The design of the business logic depends somewhat on your preference for
communcations...
</snip>
It shouldn't. The whole idea behind the business layer is that it is use
agnostic (i.e. same logic can be used from another native program call
for a screen, as a stored procedure, called by a web app, or a web
service). Communications should be handled at a layer above the business
object and this is where you will get into separate programs (perhaps in
several different languages) for each way the server programs are used.
I do agree that error handling is very important and ideally, all of the
individual servers would report errors in the same way.
Matt
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: Business Logic Servers ( was: MVC in RPG?), (continued)
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.