Hi Graeme, Many thanks for the info. LZW uses a similar dictionary structure, and it works by whacking some arbitrary limit on the dictionary size. There are some problems with this if the data patterns in the stream change, but there are various work around's for this as well. You are right in the assumption that the actual algorithm is not important - the same as with CryptoStream where the cryptography applied is not the focus.
I'll give RLE a whirl today. Thanks to Peter for his reply too. Nick ----- Original Message ----- From: "Graeme Foster" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, April 12, 2002 12:05 AM Subject: Re: [DOTNET] .NET Compression Code > On second thoughts, Zip might not be a good idea in this case. I'm no expert > on the matter, but given that a stream could potentially be infinitely long > (and you'd probably want to demonstrate the CompressedStream with something > other than a FileStream), would that mean Zip's dictionary would grow to an > infinite size, too? Or does it have some cut off point? > > I'd say your best bet would definitely be RLE - as long as you don't have an > infinitely long string of identical bytes in your stream :) > > Cheers, > G. > -- > Graeme Foster ([EMAIL PROTECTED]) > Principal Software Engineer > Aston Broadcast Systems Ltd. (http://www.aston.tv) > Disclaimer: I really don't have a clue what I'm on about. > > -----Original Message----- > From: dotnet discussion [mailto:[EMAIL PROTECTED]]On Behalf Of > Nick Wienholt > Sent: 11 April 2002 12:45 > To: [EMAIL PROTECTED] > Subject: .NET Compression Code > > > Can anyone point me to some C# (or Java) compression code that I can > distribute with a magazine article? I have a CompressedStream class that > compresses data and passes it through to an underlying stream (similar in > concept to CryptoStream), and having a working LZW implementation in C#. I > have been unable to work out one way or the other the legalities surrounding > LZW, and am after a replacement. > > > > **************************************************************************** * > The contents of this email and any attachments are confidential. > It is intended for the named recipient(s) only. > If you have received this email in error please notify the system manager or the > sender immediately and do not disclose the contents to any one or make copies. > > ** eSafe scanned this email for viruses, vandals and malicious content ** > > **************************************************************************** * > > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
