in reply to Encoding/compress CGI GET parameters

You can handle the /script.pl/dflskjdfsdkf part with $ENV{PATH_INFO} (if I'm not mistaking). Most pack() & unpack() operations will make it longer (hex 2 for 1, binary 8 for 1). CRC Modules and Compression Modules are listed on CPAN. MD5 is more about encryption (which is pretty usefull too, in this case).

Greetz
Beatnik
... Quidquid perl dictum sit, altum viditur.

Replies are listed 'Best First'.
Re: Re: Encoding/compress CGI GET parameters
by snellm (Monk) on Jan 17, 2001 at 18:54 UTC

    Hi Beatnik,

    My line of thought for integers was: There are approx 71 characters valid in a URI, which means any integer could be converted to base 71 and the resulting bytes remapped into that range of characters. With a stop byte, that means any integer greater than 5041 would save at least a byte.

    Having said that, I expect most compression to come by using a scheme where the first byte indicates the format of the data, meaning that parameter names are not neccesary.

    regards,

    -- Michael Snell
    -- michael@snell.com

[reply]

In Section Seekers of Perl Wisdom