in reply to Re: Encoding/compress CGI GET parameters
in thread Encoding/compress CGI GET parameters
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
|
|---|