No artwork

[bubbleguuum]

(22-11-2012 10:46)simoncn Wrote:  

(22-11-2012 09:53)bubbleguuum Wrote:  An alternative to gzip+base64 is to use a md5sum of the file path.
That limits URL length at the (small) expense to have to store the md5sum => file path association in a file. Which is very easily done by using Java serialization on a HashMap for example. That's what I'm doing in BubbleUPnP Server. But in other scenarios I just use gzip+base64.

The disadvantage of this would be that I couldn't decode paths in trace logs created by users for problem solving and debugging. This isn't a problem if I use a self-contained reversible encoding.

It always has to be reversible, otherwise you would not be able to get the path to stream the file (independently of logging).

In the case of md5sum, the association (md5sum, filepath) must be stored and persisted in a hash table to be able to decode the md5sum.