Re: OO extensions compatibility between v4 and v5

Thanks. I'm looking over it now though that documentation seems to be for extension developers wanting to access files through the standard streams api provided. So I either need to provide the centera functionailty at the extension developers level like: php_stream_open_wrapper("centera://localhost/FE132B626A72C220FF", "rb", REPORT_ERRORS, NULL); or what I was originally thinking was to provide it only at the userland level: <?php ... open("centera://...") ... ?> which is all we really need. I am also speaking to my boss about releasing this open source and he seems keen but just needs to confirm that we will be retaining the IP from the client so that we can release it. I dont know how useful this will be but I imagine there are some people out there using cenera storage and may have a need to get it online. Unfortunately there is a C API provided by the vendors of this harware so I cant write the extension in pure PHP. Hartmut Holzgraefe wrote:

Chad Thatcher wrote:

1. I am considering extending the standard file operations in PHP to accept a Centera URI [e.g. open('centera://etc_etc_etc')] and was wondering if this would be an onerous task seeing as the file system in question is quite unlike other file systems out there. I'm only hoping it will be trivial as the file operations already support things like http:// which are very different too.

The implementation of streams on the C level is documented in http://php.net/manual/en/streams.php If you do not need any external libraries to talk to that service you might want to try implementing your stream in pure PHP first and maybe port it to C later: http://php.net/stream-wrapper-register The WebDAV stream implementation was done this way, you can find it in PEAR package HTTP_WebDAV_Client