well - imnot sure here, but this sounds more an aspect need then a object one - however, if we would build all urls in a centralised way, at one place then it might get more easy to set up mor andvanced URL strategys and needs - e.g: even transport global parameters in restful / bookmarkable URLs without any special work needed in the particular page(s)
> -----Ursprüngliche Nachricht----- > Von: Eelco Hillenius [mailto:[EMAIL PROTECTED] > Gesendet: Samstag, 25. November 2006 20:57 > An: [email protected] > Betreff: Re: common URL encoding/ decoding (base64) > > > some time ago i reportet > > http://issues.apache.org/jira/browse/WICKET-16 > > , wich was solved fast. However, the problem consits till > today and so > > i opened up http://issues.apache.org/jira/browse/WICKET-77 > > 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. > > Well, I have been thinking along such lines for different > reasons, but the problem is the actual implementation. It's > not that easy to implement while still keeping proper object > abstractions in place. Of course, if you're able to provide a > patch that works, I'm sure everyone is interested in looking into it. > > Eelco >
