Hi Shah
This is pretty much the direction I discussed off-list with R. Gareus,
and it does indeed fix a few issues we currently have..
The changes me and Gareus ended up agreeing on, and I sent a
mail to Andy Smith (termie) to clear, was to have the parameters
-array into an array of key-value arrays so that
?a[]=foo&a[]=bar
would be represented by
array(
array( 'key' => 'a[]', 'value'=>'foo' ),
array( 'key' => 'a[]', 'value'=>'bar')
)
(Smith never replied though, which is why I never started writing the
patch needed myself)
But I might lean towards your way of doing it, after having read
though the patch.
So all in all I agree with the functionality of the patch, but I haven't
looked though the coding style yet..
The remaining issues is to actually read the parameters from get/
post in OAuthRequest::from_request.. It needs to actually override
get-parameters with any incoming from post, so some sort of
elaborate merging is needed..
Also, get_parameter's key => value functionality is now somewhat
broken, and get_parameters doesn't return a _GET/_POST-like
array, but I guess this is expendable because I don't see a way to
keep these while maintaining all variables of the request..
- Morten