|Thanks, that explains it. It's funny, whenever I email someone a Greenstone url I construct my own cleaner, short ones because the longer ones can get cut off (and thus not work) by some people's email clients. I agree, this would make a nice option in future releases.
>>> "John R. McPherson" <firstname.lastname@example.org> 09/20/07 3:02 AM >>>
On Mon, Sep 17, 2007 at 02:58:57PM -0700, Gavin Spomer wrote:
> I've always wondered why some of the urls in Greenstone are so long. What's the meaning/purpose of all those dashes, digits and other characters that make the url so long? Having done my share of online programing with php, perl, embperl and a bit of cold fusion, a url like the following makes total sense to me:
> But a url like the following has me scratching me noggin:
> Why does this url have to be so long and ugly? (not very readable)
the e=... parameter is an "encoded" version of all the settings currently
in effect. I think the idea behind it was if you are browsing, you can
send a url to someone and they will see exactly what you see, rather
than seeing something different based on your cookies or sessions.
(Eg this stores all the settings and preferences like language, query terms,
search preferences like stemming/case folding, etc).
Having said that, I've always thought it was ugly as well, and there should
be an option to not use the encoded cgi argument. I'm not sure if it's
possible to disable it. But it would be a good thing for someone to add