sounds very promising - like i wrote to eelco: if all URL things would be centralised and go through 1 place at the end (encode)/ begining (decode) then the world would be open to handle most special url needs easier - e.g: language-tag in URLs, global needed params etc.
as it could go this /lang-tag/anybookmarkable-page /lang-tag/?wicket=interface... so we could set up this without the need to limit ourself to 1 strategy all over the app... any comments from the core-programmers on this? Regards > -----Ursprüngliche Nachricht----- > Von: Jean-Baptiste Quenot [mailto:[EMAIL PROTECTED] > Gesendet: Sonntag, 26. November 2006 11:45 > An: wicket-dev@incubator.apache.org > Betreff: Re: common URL encoding/ decoding (base64) > > * Korbinian Bachl: > > > These was aimed at the missing decoding of these issues in > > pageparameters, however, I now wonder if it wouldnt be > better to give > > wicket a common URL filter wich decodes and encodes all URLs > > before they are used/ released so that these are solved forever. > > Related to that: in « WICKET-65 Handle String array in > PageParameters » I provide a generic WebRequestEncoder to > factor out the URL-encoding instructions that stand all over the code. > -- > Jean-Baptiste Quenot > aka John Banana Qwerty > http://caraldi.com/jbq/ >
