Separate Functions to Compress From Memory and From a File

Started by
20 comments, last by Ectara 11 years, 5 months ago

You're right. I'm going to drop support for all of these features, remove several modules of my libraries, and use all features that aren't supported on all of the platforms I own. I was waiting for when the first "abandon the project" post would appear.


I apologize, my sarcasm was completely unnecessary. (Don't post at 12:36am, kids.) I don't think you should abandon the project, I guess I was just echoing mhagain's thought that it really becomes a management decision as to whether it's worthwhile to support an edge case like this. I just had a hard time imagining a use case for this. That's all.
Advertisement

I guess I was just echoing mhagain's thought that it really becomes a management decision as to whether it's worthwhile to support an edge case like this. I just had a hard time imagining a use case for this. That's all.

I understand where you are coming from. I just have a platform, right here, in my hands, that does not support memory mapping through the OS, and there are many other reasons that I feel that simply using memory mapping is not the right solution _for me_. It may be the best practice for other situations, but I have long thought it over, and have recently moved _away_ from a solution where everything must reside in memory. I was just hoping to find out if anyone knows a magical 3rd solution, because I generally come here when I have examined all options that I know, and have decided that none are the best; this need not always mean that there is another solution.

This topic is closed to new replies.

Advertisement