Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is there a really simple compression technique for strings up to about 255 characters in length (yes, I’m compressing URLs)?
I am not concerned with the strength of compression – I am looking for something that performs very well and is quick to implement. I would like something simpler than SharpZipLib: something that can be implemented with a couple of short methods.
I think the key question here is “Why do you want to compress URLs?“
Trying to shorten long urls for the address bar?
You’re better storing the original URL somewhere (database, text file …) alongside a hashcode of the non-domain part (MD5 is fine). You can then have a simple page (or some HTTPModule if you’re feeling flashy) to read the MD5 and lookup the real URL. This is how TinyURL and others work.
For example:
Could be shorted to:
Using a compression library for this will not work. The string will be compressed into a shorter binary representation, but converting this back to a string which needs to be valid as part of a URL (e.g. Base64) will negate any benefit you gained from the compression.
Storing lots of URLs in memory or on disk?
Use the built in compressing library within System.IO.Compression or the ZLib library which is simple and incredibly good. Since you will be storing binary data the compressed output will be fine as-is. You’ll need to uncompress it to use it as a URL.