On 12/28/06, Kevin Newman <[EMAIL PROTECTED]> wrote:
What you have described is basic deep linking, but does not solve the problem I have been attempting to articulate. Regardless of what goes on on the server, if you enter some path info after the .com part of the url, the server thinks it is getting its data from that location (foo.com/bar/ for example).
Not quite true. You can use mod_rewrite (on Apache) to chop up the URL - everything after the foo.com/ can be altered internally to be a request to something else entirely, without affecting the browser. e.g. the client enters foo.com/bar/monkey internally, mod_rewrite alters it to foo.com/index.php?page=bar/monkey, but the user still sees foo.com/bar/monkey in his browser. I've done it lots, I know it works. :-) You can then enter your application at any point you like based on a complete URL - e.g. passing it through to Flash as flashvars via PHP. But as you say, unless we then update the browser's location bar when we move through the app, it doesn't help much. :-) Cheers, Ian
