That's right.
I did not RTFM.
I did not knew about this php.ini directive.
Like I've said, I was used to understand php procedure to handle sessions.
But some of ASP programmers was / is not...
Sorry to bring some lose of time.
[]'s
Ernani
"Dj Anubis" <[EMAIL PROTECTED]> escrev
At 05:36 02/10/2002 -0300, you wrote:
>Hi Gareth,
>
>I do not know about performance impacts
well, if you're talking about talking a script, "reading it-> editing it ->
parsing -> executing", it stands to reason that this'll have more overhead
than just "parse -> execute" and so performance
Le Mercredi 2 Octobre 2002 10:06, Ernani Joppert Pontes Martins a écrit :
> Yes I know that you can't send headers to the browser when you've already
> sent some other stuffs, but ASP users have strange feeling that this is
> weird.
That's not a PHP problem, but deals with headers and page stand
Hi Gareth,
I do not know about performance impacts
Lke I've said, that is just an idea for ASP guys to see the PHP Power.
If it impacts on performance, let them know
But this will be problem of them, just let them know that if send this
session when it is already sent, the performance
At 05:06 02/10/2002 -0300, you wrote:
>Yes I know that you can't send headers to the browser when you've already
>sent some other stuffs, but ASP users have strange feeling that this is
>weird.
php.ini : Output buffering = On
what is wrong with this?
>Can't we implement some procedure that chec
I have a sugestion..
Like some of "a lot" of designers want to use ASP scripts on server side
I have had a lot of critics about session handling on PHP.
Yes I know that you can't send headers to the browser when you've already
sent some other stuffs, but ASP users have strange feeling t
