[PHP-DEV] What to do about 4.0.5

2001-04-04 Thread Andi Gutmans

OK guys,

I feel VERY uncomfortable releasing 4.0.5 with this arg_separators problem. 
Let's brainstorm and try to think of a nice, clean and constructive way of 
solving this problem. Let's try to ditch the "screw the user because he 
didn't read RFC foo.bar approach :)
The issue is with the arg_separator of incoming URL's. If we think of a 
nice solution we should probably make it lookfeel similar to the solution 
we will have with URL's which are created.

Ideas? Thoughts?

Andi


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]




Re: [PHP-DEV] What to do about 4.0.5

2001-04-04 Thread Jani Taskinen

On Wed, 4 Apr 2001, Andi Gutmans wrote:

I feel VERY uncomfortable releasing 4.0.5 with this arg_separators problem.
Let's brainstorm and try to think of a nice, clean and constructive way of
solving this problem. Let's try to ditch the "screw the user because he
didn't read RFC foo.bar approach :)
The issue is with the arg_separator of incoming URL's. If we think of a
nice solution we should probably make it lookfeel similar to the solution
we will have with URL's which are created.

We spoke with Zeev about this. We came to conclusion that
there should be a php.ini directives like these:

arg_separator.input=";"
arg_separator.output="amp;"

Where defaults are:

arg_separator.input=""
arg_separator.output="amp;"

--Jani



-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]




Re: [PHP-DEV] What to do about 4.0.5

2001-04-04 Thread Andi Gutmans

At 05:40 PM 4/4/2001 +0200, Jani Taskinen wrote:
On Wed, 4 Apr 2001, Andi Gutmans wrote:

 I feel VERY uncomfortable releasing 4.0.5 with this arg_separators problem.
 Let's brainstorm and try to think of a nice, clean and constructive way of
 solving this problem. Let's try to ditch the "screw the user because he
 didn't read RFC foo.bar approach :)
 The issue is with the arg_separator of incoming URL's. If we think of a
 nice solution we should probably make it lookfeel similar to the solution
 we will have with URL's which are created.

We spoke with Zeev about this. We came to conclusion that
there should be a php.ini directives like these:

arg_separator.input=";"
arg_separator.output="amp;"

Where defaults are:

arg_separator.input=""
arg_separator.output="amp;"

Sounds like a good solution to me.
The places which used the old arg_separator seem to only be in main.c and 
url_scanner*.c
So we should update these and add support for the arg_separator.input.
I think that's really OK.

Andi


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]