foot. Better would be that we give
directly a choice..
add 2 extra methods to webapplication
public final void mountBookmarkablePage(final String path, final Class
bookmarkablePageClass, final Class codingstrategy)
and the one with the pagemap (but don't know about that because in 2.0 the
pagem
and pages still would work, even if there is a
param around - and since the param is stored in query, the developer can see
it and even fix it if he wants to
just my 2 cents...
Korbinian
> -Ursprüngliche Nachricht-
> Von: Johan Compagner [mailto:[EMAIL PROTECTED]
> Gesendet
yeah
it looks like you are also getting form submit parameters and the indexed
strategy cannot encode them because their names are not integers
this is the trouble with the indexed strategy
not sure how to go about fixing it
you dont have a query string because the params are part of the path
application. There isn't a sanctioned approach to organizing things into
subdirectories.
* The reliance on query parameters means that common search engines will
only see a tiny fraction of the application.
Plus (!) the important security feature that your technology is not revealed
to the
into
subdirectories.
* The reliance on query parameters means that common search engines will
only see a tiny fraction of the application.
Plus (!) the important security feature that your technology is not revealed
to the outer world, making attacks on it mor difficult (if your url is
h
)
Component C = mounted to (/C)
if a page now is called using /page/a/12/b/13
it knows that A gets a string "12" - but if a is not incorporated it does
nothing - and if there is a component A it gets it - if there is A + B A
gets 12, B 13, if there is only B it gets 13 - rest is just ignore
