$_POST instead of $_GET

[ddn]

Hi,

The datagrid makes use, for the datagrid sorting & pager parameters, of the $_GET session being visible in the URL.

Is it possible to switch this to the $_POST session?

With the "form method post" html syntax, it did not switch.

Consequently when looking into the source of "renderer.php" the function "_buildSortingHttpQuery" tells that $_POST is foreseen but not yet fully implemented.

Is this foreseen in a future version or did I overlook something?

Many thanks.

With kind regards.

ddn

[mark]

Hmm, doesn't the 'extraVars' option already solve your problem?

[ddn]

Basically I was asked to hide all parameters in $_POST.

This to avoid visible $_GET url parameters.

While extraVars adds parameters to $_GET.

Already thx anyway.

[mark]

[ddn]

Well,

The current code parses all parameters stored in the URL by the $_GET session.
Additionally if setRequestPrefix() is set, it processes only the parameters with the defined prefix.

The current Datagrid package structure has already foreseen the expansion with boolean flag implementation for either $_GET or $_POST array processing.

Followed by this logical handling to be added to the current package structure.

At initialisation time of request arguments:

If ($Flag == 'Flag_POST'){
When chosen for $_POST:
Create an multidimensional array in the $_POST array
(with a PEAR-DataGrid reserved name).
Here named "_RequestArguments" for sake of documentation.
$_POST['_RequestArguments'] = array();
Add all parameters to this array $_POST['_RequestArguments']
}
ElseIf ($Flag == 'Flag_GET' || $Flag == ''){
When chosen for '$_GET':
Just execute current code.
};

At processing time of request arguments:
If ($Flag == 'Flag_GET'){
//If chosen for '$_GET':
Just execute current code.
Parse all parameters stored in here.
Additionally if setRequestPrefix() is set,
it processes only the parameters with the defined prefix.
}
ElseIf ($Flag == 'Flag_POST'){
// If chosen for $_POST:
Foreach ($_POST['_RequestArguments'] as $Key => $Value){
Parse all parameters stored in here.
Additionally if setRequestPrefix() is set,
it processes only the parameters with the defined prefix.
};
};

Applying these changes, as you indicated in your post, do require a knowleadgable person (as yourself) who is aware or can become aware well enough of the package internals and implications.

With kind regards.
DDN

[mark]

My question was more how you would implement the "links". In the column headers we have currently normal links (using some GET params) for sorting. How do you want to replace them?

[ddn]

In pseudocode not having investigated in too much detail the package and without pretending anything at all something like this:

[ddn]

Oops typo.

Please find below correction.

[mark]

Now I'm really confused. In your first answer you wrote: "This to avoid visible $_GET url parameters." And now you show code which generates new $_GET parameters.

If your only idea is to put some $_POST params into the links for sorting (and paging), then it is likely that we decline this idea. For only some of such params, you can easily use the 'extraVars' option. And for params with huge contents (which are no problem with POST), you might get trouble anyway (GET is not meant for such things). Therefore, I don't see a need for adding *all* $_POST params to the query string.

But maybe you want to clarify what your real request is?

[ddn]

Hi,

Sorry for any confusion. Let's resynchronise.

[mark]

I'm sorry, but I'm still not sure what your real goal is. You wrote about "$_POST session management". I assume that you wanted to write $_SESSION?

Anyway, this seems to be a very special and custom request. Wouldn't just overloading the existing HTML_Table renderer work for you? You could overload some methods and implement the handling there as you need it. If needed, you could also overload the core Structures_DataGrid class.

[ddn]

Hi,

Well thanks, I'll follow up the advice.

Meanwhile the address bar url is now clean through the use of an iframe.

If circumstances allow me, I'll do and post later on the research results.

Many thx anyway for the support.

Cheers.

DDN