Hi there! I found that H2 project has a good java port LZF compression algorithm, and decided to have a look if it me reusable for my needs (on-the-fly compression of streaming data). Code looks clean and works, but I noticed one thing that I thought I should ask about. Comparing code with c version, it looks like block identifiers used are bit different in Java, compared to ones that lzf.c uses. Is this intentional? If I am not mistaken this means that output from Java code is slightly incompatible with command-line c tool. While it is not strictly necessary to retain compatibility it would seem nice if structure was in fact identical. But perhaps there are some reasons to deviate from it? (I don't know if LZF format is documented anywhere, so this just from reading source code).
Differences I noticed are the use of 4-byte header (as opposed to just use blocks with short headers), and prefixing blocks with 4-byte length marker (negative for uncompressed, positive for compressed) instead of 2-byte marker/1-byte type/2-type length. Both mechanisms of course work, they are just different. -+ Tatu +- -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
