Applying HTTPAPI and eXpat updates - seeking advice

["Koester, Michael" <mkoester@xxxxxxxxxxxxx>]

We have a couple mission-critical applications using LIBHTTP, which hasn't been messed with in 4 years (appears to be version 1.24, without the SSL option).
 
I now need to extend the capabilities to handle TLS (aka SSL) communications, and after a few tries, I now have a test of that working successfully in library LIBHTTP2 (which is version 1.29).

I don't believe I have any custom mods in LIBHTTP, but since the initial foray into HTTP & EXPAT stuff we also implemented a project that used Thomas Raddatz' WSDL2RPG work.  I don't know if that has hooks into LIBHTTP or not.

So now I need to integrate the updated v 1.29 with SSL into LIBHTTP.  Can't run both in Production without LIBL problems.

My hope is that I can delete LIBHTTP2, and run INSTALL (of v1.29 with SSL) to LIBHTTP as the target library.

After doing that, can I expect that the existing applications should continue to run without having to recreate objects in the existing applications?  I'll create the objects for my new functions after LIBHTTP is updated -- I'm mainly concerned with the existing applications. 

Many thanks,
Michael Koester

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------