Any thoughts about implementing Apache's mod_rewrite functionality (so that search engines can index dynamic sites) so that SM modules can get their invars from something other than GET, POST, or SESSION?
Maybe this is unnecessary since so many sites run on Apache anyway, but some hosting packages don't offer easy access to the apache conf or htaccess.
What do folks think? Worthwhile? Any thoughts on where/how to do it? Maybe re-implement inVarManager or something like that?
Thanks and regards,
Dave
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You could just store vars in the session container in one mod and read them out in the next .... kind of the same thing.
Making siteManager specific to Apache might make things difficult for some - certainly when they develop because most people seem to do this on an MS box and then upload to a linux server, and they don't use Apache on their local machine.
... just my 0.02 worth...
Mike
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I wasn't suggesting that SM be made Apache-specific. Like you, I do my development locally on Windows and then upload to a (typically) Unix host online. I mentioned Apache only as a specific reference for mod_rewrite functionality.
Your suggestion for implementation is pretty interesting: So, write a single module (say, called modRewrite) that unwraps the vars in the pathinfo and dumps them into session vars? Any module (say, myModule) that needs to access these vars simply calls modRewrite before accessing the vars, maybe in moduleConfig.
Does this sound right?
Thanks and regards,
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all,
Any thoughts about implementing Apache's mod_rewrite functionality (so that search engines can index dynamic sites) so that SM modules can get their invars from something other than GET, POST, or SESSION?
Maybe this is unnecessary since so many sites run on Apache anyway, but some hosting packages don't offer easy access to the apache conf or htaccess.
What do folks think? Worthwhile? Any thoughts on where/how to do it? Maybe re-implement inVarManager or something like that?
Thanks and regards,
Dave
You could just store vars in the session container in one mod and read them out in the next .... kind of the same thing.
Making siteManager specific to Apache might make things difficult for some - certainly when they develop because most people seem to do this on an MS box and then upload to a linux server, and they don't use Apache on their local machine.
... just my 0.02 worth...
Mike
Hi Mike,
Thanks for the ideas.
I wasn't suggesting that SM be made Apache-specific. Like you, I do my development locally on Windows and then upload to a (typically) Unix host online. I mentioned Apache only as a specific reference for mod_rewrite functionality.
Your suggestion for implementation is pretty interesting: So, write a single module (say, called modRewrite) that unwraps the vars in the pathinfo and dumps them into session vars? Any module (say, myModule) that needs to access these vars simply calls modRewrite before accessing the vars, maybe in moduleConfig.
Does this sound right?
Thanks and regards,