On Thu, 5 Jul 2007, William A. Rowe, Jr. wrote:
> Stanislav Malyshev wrote:
> >> something isn't clear to me: Is php as apache module supposed to work
> >> without problems - if compiled as zts - only on apache worker or even
> >> on apache prefork?
> >
> > I think if you manage to compile it tha
Stanislav Malyshev wrote:
>> something isn't clear to me: Is php as apache module supposed to work
>> without problems - if compiled as zts - only on apache worker or even
>> on apache prefork?
>
> I think if you manage to compile it that way it might work, but I don't
> really see why you would w
Writing an extension with maintainer zts enabled is a good way to ensure
you remembered to add the needed TSRM stuff.
Right, that's a good idea to check extension in TS mode. However, I'd
not run TS module in prefork beyond testing.
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECT
Writing an extension with maintainer zts enabled is a good way to ensure
you remembered to add the needed TSRM stuff.
Scott
Oliver Block wrote:
I think someone recommended me to compile --with-maintainer-zts, because
I was working on some functions within the imap extension.
That's the main re
I think someone recommended me to compile --with-maintainer-zts, because
I was working on some functions within the imap extension.
That's the main reason.
Regards,
Oliver
Stanislav Malyshev schrieb:
something isn't clear to me: Is php as apache module supposed to work
without problems - if
something isn't clear to me: Is php as apache module supposed to work
without problems - if compiled as zts - only on apache worker or even on
apache prefork?
I think if you manage to compile it that way it might work, but I don't
really see why you would want to do it - TS build is slower.
-
