Cpt John W. Holmes wrote:
Agree 100%. Don't assume that just because you use JSP, or any other
language, your program is going to instantly "scale well" and be easy to
maintain. You can write crappy, inefficient code in any language. You can
also write good programs in most any language if you put the proper planning
into it before hand.

Ok, I've got answers concerning the learning curve and maintainability and some pros and cons that I have found very useful.


Now the one last point that I would like to really find out about is persistence. I keep hearing that you can get *true* persistence with jsp/servlets/beans/whatever. I'm still trying to find out more details on this as I can't see how you can get that since HTML is stateless and whatever the backend is it all eventually turns into an HTML connection ...

Sessions in PHP are nice but as everyone knows they don't allow for true persistence. And if you want to have your objects persist over a session, that's even more work (and in my short programming career I have not yet found a case where persisting a PHP object across a session was worth the trouble/overhead).

Can anyone offer an opinion on this? Is persistence with jsp that much easier compared to PHP? And if true persistence is possible is it all it's cracked up to be?

I've often dreamed of being able to have true persistence but if I had it maybe I wouldn't find it all that useful once I'd had a go with it.

Thanks,

Jean-Christian Imbeault


-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php



Reply via email to