Comparing PHP and JSP...

[Anon]

Hi
I like a lot PHP. But I have also been reading a lot about JSP and I am getting curious about how PHP handles some situations JSP needs the programmer to handle. For example, JSP needs the programmer to create a pool of DB connections in order to keep the site fast. PHP seems not to take care of those things. Why? Does PHP already take care of those issues automaticly? How does PHP do that? There is also the syncronization issue also. How does PHP take care of that? Thanks...

Rodrigo Reyes

PS. Sorry about my English. It is not my native language.

[Anon]

Hello,
i'm only reading about JSP and playing nicely with Java servlets, but :

Database connections:

Due the performance bottleneck of establishing a database connection pools are a appropiate mean to solve this.
The PHP has an integrated Connection-pool for persistent database connections. I think you are not in the situation having the same connection to the database than in Java.
Therefore the handling of many queries in a long transaction over many PHP-pages will be very uncomfortable.
Java lets you the choice about the the use against the dbserver or other services.
There are many libs with this functionality.
Due the scriptlanguage character of PHP the _pconnect-function ist sufficient for the allmost purposes on simple websites.

synchronisation:
Do you mean the synchronisation of threads/tasks ?
Due PHPs turing-computabilty you can do all do the same as with other languages : theoretically.
The implementation of concurrency is not supported by the PHP language itself, such as Java or Ada.
You have to implement your own system with native OS-calls and/or Javascript-functions that running other PHP-scripts (or with other) parameters in another browser window/frame/layer.
I think it's hard to code and not the design goal of PHP.

Regards
Ingo

[Anon]

Ingo
So what you mean is that PHP only has a pool of connections for persistent connections? That is, normally (as I normally code, I mean) you stablish a connection and then it gets closed every time you run your PHP code. Could that become a bottleneck? Is it better to use persistent connections and the pool PHP already has?
About synchronisation, what I meant is that I think in JSP you have to synchronise your access to the DB (I used JSP long ago, so I may be wrong about this), but I never found anything about that in PHP. In other words, what exactly happens when you try to access a DB from two different connections, both in PHP and JSP? Hope you know. Nevertheless, thanks...

Rodrigo

Ingo Oellers wrote:

Hello,
i'm only reading about JSP and playing nicely with Java servlets, but :

Database connections:

Due the performance bottleneck of establishing a database connection pools are a appropiate mean to solve this.
The PHP has an integrated Connection-pool for persistent database connections. I think you are not in the situation having the same connection to the database than in Java.
Therefore the handling of many queries in a long transaction over many PHP-pages will be very uncomfortable.
Java lets you the choice about the the use against the dbserver or other services.
There are many libs with this functionality.
Due the scriptlanguage character of PHP the _pconnect-function ist sufficient for the allmost purposes on simple websites.

synchronisation:
Do you mean the synchronisation of threads/tasks ?
Due PHPs turing-computabilty you can do all do the same as with other languages : theoretically.
The implementation of concurrency is not supported by the PHP languag....