Confusing you was one of my goals ;-) just kidding.
The issue is the installation. A normal Zendcore setup does not respect
certain security settings for different user groups to separate their
data. It is rather easy to peek into other users sources / data if one
does not pay attention.
As we are not THAT experts in PHP and Zend, we contacted them here in
germany (i personally know some of the sales people) so they routed me
to technical staff. Had some discussions, we offered a playground to
them to review these issues - not much reaction. Some technicians left
Zend, others restarted the review, came back later with some statements
about the free Zend community edition on i will not be supported on that
detailed base....
It is a long story which ended in no perfect results. We do not have the
time at the moment to fiddle around with all that stuff, Zend doesnt
seem to have time, too.
If someone on this list is willing to do so and has some time and
expertise, we can create a little LPAR as a playground to work with Zendcore
(or with raw PHP, why do we need to use Zend? ;-) and see what is needed
to be done, so we can create a common community setup.
-h
Am 09.06.15 um 01:33 schrieb Jon Paris:
You have confused the heck out of me with this Holger.
First IBM i is a huge part of Zend’s revenues so I can’t see how you can possibly say they are “not interested”.
Second - why do we need to set up PHP at all? It is free on IBM i - IBM pays for it and installation is the same as any other product - what’s the problem?
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
On Jun 8, 2015, at 7:23 PM, Holger Scherer <hs@xxxxxxx> wrote:
Talked to the Zend people - forget them, they're not very interested in the i platform. So we need to setup PHP manually, but will be done soon.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.