-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonathan,
On 3/20/2009 7:53 PM, Jonathan Mast wrote:
Meh. Most Java webapps aren't multithreaded anyway in the sense that
each request lives in its own little world and usually runs start to
finish with no other threading involved.
Just this
I would argue that, architecturally, this kind of work doesn't belong in
the request processing portion of the application. I generally do this
kind of thing with cron jobs. Otherwise, you can have HTTP requests
kicking-off lots of long-running processes. That may be possible in
Java, but I'm not
Number of users is not the only one thing, you need to think about, when you
are choosing technology.
PHP is a _scripting_ language with out of _static typization_,
multi-threading, full OOP support and its API is pretty weak too.
Also it is _not_ designed for servlet ideology: each request runs
Just ask them to google for security-issues linked to PHP and issues
linked to any servlet-container (aka Tomcat).
If they want it more specific, ask them to read through some relevant
mailing-list-archives such as full-disclosure.
OK, that's not about performance, but we f.e. do not use PHP due
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ilya,
Don't get me wrong... I loves me some Java. But...
On 3/20/2009 11:55 AM, Ilya Kazakevich wrote:
If you are going to move to php, be ready to:
1) loose tools like log4j.
log4p?
2) meet API, 10% of which uses OOP and exceptions, and 90% is
Meh. Most Java webapps aren't multithreaded anyway in the sense that
each request lives in its own little world and usually runs start to
finish with no other threading involved.
Just this week I added threading to a component of my web-app. I had some
what dreaded it, but found that it took me
