I have written a C++ extension for php which accesses
an external .so proprietary data engine.
The extension basically works, but the engine - reliable
when accessed outside php/zend - is generating stream
based errors, possibly due my poor understanding of the
streams/threading requirements in such a scenario, via zend.
Rather than struggling with an area that is unfamiliar to me,
I would prefer to work with a zend engine guru as consultant,
to:
a) resolve the current issue,
b) recommend a safe and appropriate code structure for both the extension
and the external
object,
c) code review the extension (and as appropriate, the proprietary
data engine) prior to commercial release.
If there is anyone either willing to undertake such work,
(preferably/ideally in London/UK) or knows someone,
could they let me know?
---
If anyone should care to comment in principle on the matter,
the code structure can be summarised as follows:
1. A C++ object compiled into a non-extension .so shared object
opens a disk file using fcntl function.
2. Such an object is created and stored as a singleton global
object in a c++ file that is part of the extension.
3. Php/Zend objects are created with pointers that point to that
singleton object.
4. Operations via php or the php extension operate on the file from
within php by means of that object.
The externally compiled object does not use the zend streams api.
Cheers,
Andrew.
