On 10/11/06, Frank Bille <[EMAIL PROTECTED]> wrote:
But shouldn't the page be bookmarkable then? How else are you going to make use of that externalized component? Except if I have got your concept of "externalizing" wrong (= bookmarkable)
No this externalizable thing only means that 'state' is being passed as part of the URL. So an URL like this http://localhost:8081/tsp/web?wicket:interface=_wf_component:1:10:1: could be something like http://localhost:8081/tsp/web?wicket:interface=_wf_component:1:10:1:&wicket:state=dfskajkladsjf676sdfa where that state is an encoded set of parameters. That encoding could be overridden to make them look nice (but less efficient) on a component basis (ParameterUrlEncoder), so that it could look like http://someserver/foo/bar/books/Brave_New_World Where books,Brave_New_World is what is contributed by the component, and points to a bookmarkable page mounted at /bar/books. Also: please note that I'm still thinking about this. It would be more helpful to think with me how we could pull this off, then to try to find things why it couldn't work. IMO, if we can implement this, it would be a huge potential improvement in our scalability and bookmarkability options. Eelco
