Hey Anthony, 2008/12/3 roja <[EMAIL PROTECTED]>: > Cheers for sorting all this :) Out of interest is there an easy way of > causing the wthttp to deploy the application with a name i.e. > > http://0.0.0.0:8080/name
You can use: --deploy-path=/name ? > Also, is there anywhere on the roadmap where the system will shift to using > simply urls (i.e. http://0.0.0.0:8080/internal/path/goes/here)? When deploying like you indicate above, the internal path URLs will be of the form: http://0.0.0.0:8080/name/internal/path/goes/here (instead of ?_=/...) But the displayed URL will still be: http://0.0.0.0:8080/name#/internal/path/goes/here The reason is that you cannot change the url without doing a full page reload, unless you only change behind the '#' (originally used for named anchors). This anchor trick is becoming very popular for AJAX applications. If you do not mind full page reloads (and possibly new sessions), then you could still use Wt although you lose the interactivity advantage. Then we would probably want to add a configuration option where you disable the 'canonical url redirection' that redirects the user to a URL with the '#' notation for internal paths ? Regards, koen ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
