I've managed to find my altered binder source for our custom version of
HTTPAPI, and it was indeed done to create an HTTPS-enabled version that
would be drop-in compatible with a non-HTTPS version 1.21 (at the
expense of it being drop-in compatible with any other HTTPS-enabled
version).
And it looks like it would be easier than I thought to update this to a
more recent HTTPAPI.
I'm currently reading up on service program creation and binder
language. And I'm not sure I understand how multiple STRPGMEXP blocks
work, or how the PGMLVL parameter works with regard to them. Can
somebody point me to something that will explain it in terms even my
aging "little grey cells" can process?
--
JHHL
This mailing list archive is Copyright 1997-2025 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
