Hi Scott,
What is the specific problem you're seeing? It might be a Quercus bug.
PHP 5 should only be an extention of PHP 4, so all PHP 4 applications
should work fine. It might be a bug in Quercus.
Thanks for your response. I'm not familiar with PHP, so at this
point unfortunately I
again i would say do all the experimentation w/ a mod-php5 box first.
you may be able to push the original application developers saying something
like,
'we put it on a mod-php5 box and it isnt running'.
ask them if its supposed to run on mod-php5.
as for the list of app frameworks that run on
Ok. There's a decent chance it's a Quercus bug, then.
if the app doesnt run under mod-php5, how can you blame quercus?
i mean what is the stance of quercus, is it supposed to emulate mod-php4 and
mod-php5
or just mod-php5?
-nathan
On 6/14/07, Scott Ferguson [EMAIL PROTECTED] wrote:
On Jun
Scott Ferguson wrote:
Our main development goals for Quercus for the rest of the year are
working towards getting 100 PHP applications running on Quercus and
closing bugs as they're reported.
Cool. Well I'd really appreciate news when Pligg is ok (the PHP Digg
clone).
Its at
I must confess I still don't understand why anyone would use anything
other than MOD_PHP for PHP?
Anyone who's not using Apache.
In our case we're using Resin because we started out
with a Java web application and Resin serves us well.
Then, we need to add an application in PHP4, and
if we
PHP4 is well supported/understood and is relatively easy to scale
i agree w/ you on the understanding part, but its the scalability part that
isnt so easy.
most people think to just throw hardware at the problem, but what they dont
realize is php,
being a scripting language has some memory
Nathan Nobbe wrote:
Fred,
i like what yong has to say on this one. i just got a new job a couple of
months back and was shocked to find
the company still deep into php4 w/ no strategy to move to 5.
PHP4 is well supported/understood and is relatively easy to scale.
I must confess I still
[EMAIL PROTECTED] wrote:
I must confess I still don't understand why anyone would use anything
other than MOD_PHP for PHP?
Anyone who's not using Apache.
In our case we're using Resin because we started out
with a Java web application and Resin serves us well.
Then, we need to add an
There are scenarios where php4 code will not run on a php5 system.
php5 has magic functions that are not defined in 4 (there could be
collisions here),
also there are new functions in the standard api that are new (possible
collisions here)
php5 defines object that are not defined in 4; like
Thanks very much Nathan
for your reply.
Very useful and much appreciated.
We'll evaluate our options based on the issues that you raised..
Cheers,
Fred
--
[EMAIL PROTECTED]
___
resin-interest mailing list
resin-interest@caucho.com
Hi,
I have a site using PHP4 that I would like to run under Resin,
because I also have J2EE applications already running under Resin
and would like to keep it all under one roof.
I tried using Quercus but have run into problems. AFAICT, Quercus
supports PHP5 and that may be causing the errors.
Fred,
i like what yong has to say on this one. i just got a new job a couple of
months back and was shocked to find
the company still deep into php4 w/ no strategy to move to 5.
although 6 doesnt have a clear deadline, i would assume it is only a matter
of time. and i would not like to be
in
Hi Yong, Nathan,
Thanks for your responses. Sure, ideally the site would move to PHP5 but
I don't know if that's possible in the short term. Assuming that it's
not, I
was hoping for another possibility to get the site working under PHP4
within Resin. Any ideas?
Thanks again!
Fred
On Tue, 12
13 matches
Mail list logo
