Why PHP? Since the web/browser combo has been essentially stateless,
using PHP or any backend language for sessions allowed a way to save
the state (like a login) on the server side. Saving state on the
client with Javascript or cookies is notoriously unsecure.
PHP, Ruby on Rails, and others have done both the display and business
logic extremely well. But to me, their value is increasingly on the
server, for business logic. For clients doing data exchanges, the RIA
(rich internet application) model is the better way to go, IMO. AJAX
is a part of that family.
-- Cole
Nathan Lane wrote:
At the top level, where my XHTML is, Is there a reason for me to use PHP? I
don't need any content management systems, and I require JavaScript to be
enabled (or I might switch a bunch of it to server side JavaScript).
I always use php at the top level on my pages for session validation.
When I write web apps my users need to log in. So I use php at the top
level to see if they are logged in and allowed on that page. I also
make certain option available based off of their login credentials.
I often use php at the top level to create the forms.
Kyle
_______________________________________________
UPHPU mailing list
[email protected]
http://uphpu.org/mailman/listinfo/uphpu
IRC: #uphpu on irc.freenode.net
