|
As I work with more and more APIs, I want to wrap them in my own procedures. I want to make these procedures available to others in my shop; service programs seem just the ticket. My first thought was to wrap each API "family" in it's own service program, so I'd have one service program for user spaces, one for retrieving program information, etc. This seems a fair balance because a single program will only need to bind to a few service programs in order to work. 1) Any contrary ideas? 2) Any practical experience to support/refute this plan? Buck Calabro Commsoft; Albany, NY Visit the Midrange archives and FAQ at http://www.midrange.com "As a rule, men worry more about what they can't see than about what they can." -- Julius Caesar
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.
midrange.com
