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
jk bericht-
Van: George Whiffen [mailto:[EMAIL PROTECTED]
Verzonden: Friday, May 30, 2003 4:27 PM
Aan: [EMAIL PROTECTED]
Onderwerp: [PHP] Sessions can be dangerous
Dear All,
There doesn't seem to be much discussion of the disadvantages and long
term dangers of using php "sessions". S
-Oorspronkelijk bericht-
Van: George Whiffen [mailto:[EMAIL PROTECTED]
Verzonden: Friday, May 30, 2003 4:27 PM
Aan: [EMAIL PROTECTED]
Onderwerp: [PHP] Sessions can be dangerous
Dear All,
There doesn't seem to be much discussion of the disadvantages and long
term dangers of using php "sess
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
Dear All,
There doesn't seem to be much discussion of the disadvantages and long
term dangers of using php "sessions". So let's redress the balance:
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-s
6 matches
Mail list logo
