Parameters as /param-name/param-value over traditional query strings

[Chris Colman <ch...@stepaheadsoftware.com>]

I've been using wicket for quite some time now and I just have a
question regarding the reason why wicket parameters are sent as a
sequence of

/param-name/param-value/

pairs instead of the traditional ?param-name=param-value& etc., query
strings.

Was the reason that it was believed that /p/v pairs are more search
engine friendly that traditional query strings?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Parameters as /param-name/param-value over traditional query strings

[Igor Vaynberg <ig...@gmail.com>]

On Thu, Mar 6, 2008 at 2:33 PM, Chris Colman
<ch...@stepaheadsoftware.com> wrote:
> I've been using wicket for quite some time now and I just have a
>  question regarding the reason why wicket parameters are sent as a
>  sequence of
>
>  /param-name/param-value/
>
>  pairs instead of the traditional ?param-name=param-value& etc., query
>  strings.
>
>  Was the reason that it was believed that /p/v pairs are more search
>  engine friendly that traditional query strings?

yes. there was a big user movement to make wicket very search friendly
by default. however, i think we made a mistake by using /name/value/
encoding by default. i am hoping in 1.4 we can back off a bit and use
query string by default, leaving /name/value/ as an explicit option.

-igor



>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>  For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org