When you reply please include the list in the recipients! Andrew Scott wrote:
Well at least I know that there are a few developers in here that are not very savvy when it comes to Enterprise Solutions with J2EE then.
That's a fair point, but rather than pointing it out it would be helpful if you elaborated on your points rather than taking the "if you don't know then I'm not going to tell you" approach.
Multiple instances, what do you think this means or I guess you don't have the concept of instantiation?
Again, meaning what? Running several copies of the application on a single server? Why would I want to do that?
I am aware of the installation package for php for windows, but why is it not part of the main package to begin with, why a separate package. I asked this once before and was told because of security issues, can only go by what I have been told. I did say correct me if I am wrong!
Ok, let's start with the "main package". For PHP the "main package" is the source code. You're clearly not very familiar with the way software is distributed in the OSS world. In addition to the source code the PHP site generously distributes two other packages for the Win32 platform - a zip file and an installation package. Personally when I'm forced to use Win32 as a server platform I always use the zip package because I'm very picky about what gets installed where.
As for the security issues I'm not familiar with any security issues that arise from using the installation package. If there were any I'm sure they would have been published and almost certainly fixed by now.
As far as Shared hosting, I can only say that you have led a sheltered life in your development cycle and don't know that applications that run in a shared environment such as one server running 13 websites can be a security risk. I think that if you understood what J2EE is all about first, then I wouldn't be having to explain myself on what J2EE is in depth.
Hmm, maybe I have led a sheltered life. I mean I've only been involved with hosting companies for the past 15 years and have been running my own hosting company for nearly 9 years, what would I know?!!
I won't disagree that shared hosting environments have a lot of implications for security. I won't disagree that I don't know very much about J2EE. What I would question is your assertion that J2EE provides any extra security in a shared hosting environment than you can get with any other system if the server is properly set up and your application takes reasonable precautions. Having your application on a shared server is never going to be as secure as having your own dedicated server just as much as having a dedicated server in a third parties facility will never be as secure as hosting it in your own facility.
Again if J2EE does provide extra security that cannot be achieved with PHP please let me know. I urge you not to come back with another "J2EE is better" but rather to explain why with specific features that make it better.
-Stut -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
