On Fri, 30 May 2003, George Whiffen wrote:
> 1. Heterogeneous Code Environments
> php session data is not easily accessible from non-php code e.g.
> Perl/C/ASP etc. In contrast, either client-stored data e.g. cookies,
> hidden posts, get variables, or data stored in a structured database
> table,
on 31/05/03 1:26 AM, George Whiffen ([EMAIL PROTECTED]) wrote:
> 1. Heterogeneous Code Environments
> php session data is not easily accessible from non-php code e.g.
> Perl/C/ASP etc. In contrast, either client-stored data e.g. cookies,
> hidden posts, get variables, or data stored in a structu
Wim
While I do see the usefullness of sessions, I have to disagree with you
on the security aspect. A session ID is just as vulnerable to sniffing
as is a username / password combination. The only security you gain from
using it instead is that it's value is time limited. If your application
reall
George,
Having created an invoicing system using php , I very clearly understand the
advantage the session construction holds : the information is maintained on
the server, rather than floating around in cyberspace between the client and
server each and every time you exchange information.
If you
Some great points in here George - but it leaves me hanging
What are the options? If we are not to use a 'state-ful' system, how do you
track users preferences, login/logout states, shopping baskets, and other
items that need sessions or some other type of reliable tracking method?
Not that
5 matches
Mail list logo
