|
> For instance, I just got done writing one service program that takes care > of all our XML processing. Behind the scenes the service program is > accessing many files, but the interfaces I export are purely functional to > the programmer. One example would be EDI_processXMLReq(xmlFile); - that > will receive in an XML file, parse it, log it, dispatch the appropriate > business logic program to process it, and return an XML response. Within > the EDI service program I access all of the files directly with CHAIN's > READ's etc. This gives me the same separation that I had in my CstMstPF > service program except for it provides services or actions instead of just > file access. Just echoing Aaron's statement. This is what we do also, this works out very well. AddCartonToSkid( Skid# : Carton# ) Carton# = NextSkidCarton( Skid# ) Serial# = CartonSerial#( Carton# ) DateShipped = CartonShipDate( Carton# ) etc. Application program concentrates on what needs to be done, the service program worries about how to do it and where the data is stored. Also makes it very easy to change your file layouts without affecting your application programs. Takes a little extra time, but well worth it. Rick
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.