compressed_image_transport: Compression/decompression functions as stand-alone lib?

[airballking]

Hi,

I have an application in which I need the beef of this function as a stand-alone function without the plugin machinery around it. Basically everything but the last call to the user-callback. Instead, I'd return the decoded image pointer.

My first impulse was to just copy-and-paste it out, but then I realized that others might be interested in such a function, too. Hence, my question: Would it be meaningful to have this decompression code (and its corresponding compression code) in separate functions in a stand-alone lib? If yes, would you be will to review and merge a pull request? If yes, I'd be happy to provide it. :)

Cheers,
Georg.

[airballking]

@dgossow Would you be interested in such a pull request?

[dgossow]

sounds like a reasonable suggestion. I will review the PR if you want to do the refactoring.

[airballking]

Great. Then, I'll go ahead, and work on the PR.