Thanks man, thanks for extensive reply.
I was aware that PHP is a server side processor, there was a typo in my post 😉 I meant "server" not "browser", but doesn matter now 😉
I found a neat function called session_cache_limiter and session_cache_expires (off my head) , they effectively eliminate caching per page, they validate a document for a time range of 180 minutes by default, i.e. the browser gets a header telling it, that the page will expire in two hours, so it doesn't attempt retrieving it from the server. Very nice 😉
After working with Cold Fusion for 3 years, I stopped seeing anything attractive in it, frankly. I am a C++ programmer, so for me it makes more sense to use PHP and not the awful <CF... tag syntax. There are more reasons by which i can OBJECTIVELY name CF as inferior to PHP, one of them is XHTML incompliency of CF - lone tags cannot be ended with /> while PHP uses what is known as XML server side application ( <? ... ?> ). Also, Cold Fusion is commercial application server costing more than 2000$, webspace providers usually steer away from it, while PHP is everywhere, and I as web developer dont have to sit on the phone support finding out what and where about CF. REgular Expressions in CF are something out of their own heads, only partialy supporting Perl syntax. The few things I appreciate about Cold Fusion are:
1) CF parses content between its tags, while PHP parses content only within its XML application tag definition (<?php ...),
2) CF is very fast, at least not much slower than PHP (I believe PHP is faster in many functions, i.e reg exp, etc)
3) CF abstracts SQL database access, which i think is a very good thing to do, as SQL standard should be better supported and perhaps, enjoy a strict ratification like XHTML and CSS
Thats it.
Sticking to PHP though 😃
Cheers.