Need a copy of php4ts.lib for Win32

From: Date: Thu, 24 Feb 2000 13:17:23 +0000
Subject: Need a copy of php4ts.lib for Win32
Groups: php.version4 
Request: Send a blank email to php-version4+get-10828@lists.php.net to get a copy of this message
Hello -- Can someone please send me a copy of php4ts.lib from the PHP4 beta 4 patchlevel1 build? Assuming that SAPI itself is stable, this should be sufficient for my work going forward. Also, is there any written documentation on PHP4 SAPI? Please pardon my ignorance. I am brand new to PHP -- I have never even used it. My main job is as O'Reilly WebSite Pro (http://website.oreilly.com/) web server lead developer, so I have my hands full with that and necessarily leave back-end stuff (PHP, Cold Fusion, iHTML, etc) to others. PHP4 works just great on WebSite Pro as a CGI prog, however we want only the best for our customers... so... Since Shane Caraveo is no longer active, I want to complete his work on the PHP3 SAPI provider for WebSite, turning it into a PHP4 provider as necessary. In his words: "...The implementation for WSAPI was much easier to do than the ISAPI implementation [...] I've attached the original WSAPI implementation I wrote. This was for the never released php3.1, and may be very different from the php4 sapi." I don't want to "gear up" with all of the build tools (Cygnus etc.) needed to make PHP4 here... all I need are the relevant H files (which I have from the PHP4 source kit), the PHP4 binaries, and the php4ts.lib file for the dynamic linkages back into the PHP machinery. By the way, this file should probably be shipped with the binaries, as well as the relevant H files, so as to allow others to develop SAPI providers without having to build PHP itself (a major process on Win32!). Thanks to anyone who can send me a copy of php4ts.lib. And thanks to anyone who can give me pointers to SAPI docs, or hints on writing a SAPI provider, (I can read sources and of course the CGI and ISAPI providers are in the sources...). -- Bob

« previous php.version4 (#10828) next »