Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:24230 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 66917 invoked by uid 1010); 29 Jun 2006 16:48:03 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 66902 invoked from network); 29 Jun 2006 16:48:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Jun 2006 16:48:03 -0000 X-PHP-List-Original-Sender: an.dromeda@btconnect.com X-Host-Fingerprint: 194.73.73.228 c2bthomr12.btconnect.com FreeBSD 4.7-5.2 (or MacOS X 10.2-10.3) (2) Received: from ([194.73.73.228:24228] helo=c2bthomr12.btconnect.com) by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP id FD/81-15023-04404A44 for ; Thu, 29 Jun 2006 12:48:02 -0400 Received: from VaioCen (host81-138-95-202.in-addr.btopenworld.com [81.138.95.202]) by c2bthomr12.btconnect.com (MOS 3.7.4b-GA) with ESMTP id AVN80272; Thu, 29 Jun 2006 17:42:36 +0100 (BST) Message-ID: <000801c69b9b$c56080f0$ca5f8a51@VaioCen> To: "Internals PHP Mailing List" Date: Thu, 29 Jun 2006 17:47:52 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C69BA4.2538D060" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Subject: -- zend engine guru/consultancy required -- From: an.dromeda@btconnect.com ("Andrew Mather") ------=_NextPart_000_0005_01C69BA4.2538D060 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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,=20 b) recommend a safe and appropriate code structure for both the = extension and the external object,=20 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. ------=_NextPart_000_0005_01C69BA4.2538D060--