I just sent an email about the use of streambuf's in this library. I think that compression would work well as a streambuf filter. That is, something like class compresionbuf : streambuf_type { public: compressionbuf(streambuf* underlying); .... } This would apply the compression algoritym (whatever you want to use) bytes put into the compressionbuf would be compressed according to what ever algorithm you're using and then sent to underlying. Similarly requests to get bytes from compressionbuf would get bytes from underlying and apply whatever decompression algorithm is desired. Note that such a class would be usable with both iostream and binary_iostream. On May 30, 2007, at 9:56 AM, Richard Hadsell wrote:
Ares Lagae wrote:
The binary_iostreams library does not try to modify the traditional iostreams classes, because this is indeed very difficult or impossible. The binary_iostreams library is a new hierarchy of classes developed to be very similar to the iostreams hierarchy. The actual implementation is quite simple.
As long as it can read and write compressed data in binary format, we'll be happy. Maybe it was the compression filters that seemed to be incompatible with binary format.
-- Dick Hadsell 914-259-6320 Fax: 914-259-6499 Reply-to: hadsell@blueskystudios.com Blue Sky Studios http://www.blueskystudios.com 44 South Broadway, White Plains, NY 10601
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/ listinfo.cgi/boost