Re: [PHP4BETA] SAPI

> About future improvements to this library, as I told Rasmus, our original > intention of making SAPI a de-facto standard for Web server modules does > not stand any chance, in my opinion. The change in my perspective mostly > happened because of my experience with COM. Knowing the way Microsoft > does stuff nowadays, and how it instructs developers for MS platforms to > develop, an abstraction layer of this sort will not be very attractive. > All IIS extended functionality is supposed to be added through COM > (including scripting languages, through IActiveScript*). Such an > abstraction layer would be cool for developing simple modules, or > developing modules that are targetted at being multiplatform, but > switching to that library from COM programming has serious drawbacks for > Win32 programmers, so I don't think that it'll ever become the de-facto > standard for writing extension modules for web servers. I still don't understand your logic here. If SAPI can cover ISAPI, NSAPI, Apache API, WebSite and perhaps Roxen, then we have 95% perhaps of the servers on the Net covered. I don't see what COM has to do with this. SAPI would be something that a software developer looking to make his module portable would look at. If he built his module exclusively as a COM object, then he obviously doesn't care about portability and as such SAPI is irrelevant to him, and that is perfectly fine. -Rasmus -- PHP 4 Beta