+- Hack Forums (https://hackforums.net)
+-- Forum: Tech (https://hackforums.net/forumdisplay.php?fid=444)
+--- Forum: Coding (https://hackforums.net/forumdisplay.php?fid=151)
+---- Forum: Software Development (https://hackforums.net/forumdisplay.php?fid=118)
+---- Thread: [.NET] Streamer - A stream wrapper with many features.. and more to come (/showthread.php?tid=5745992)
Streamer - A stream wrapper with many features.. and more to come - Barret - Oct 31, 2017
Library that wraps around the memory stream combined with the following features
Compressions
- Streamer.Compressors.GZip (Built-in, Allround)
- Streamer.Compressors.Bypat (Custom, Media files)
- Streamer.Compressors.RLE (Custom, Text files)
Encoders
- Streamer.Encoders.Base64 (Built-in, Allround)
Wrappers
- Streamer.Wrappers.File (Custom, Allround)
- Streamer.Wrappers.Null (stream debugger)
Serializers
- Streamer.Serializers.Binary(Of T) (Built-in, Allround)
Hash Generators
- Streamer.Cryptography.KeyedHash (Built-in, Allround)
- Streamer.Cryptography.MD2 (Custom, Allround)
- Streamer.Cryptography.MD5 (Built-in, Allround)
- Streamer.Cryptography.RIPEMD160 (Built-in, Allround)
- Streamer.Cryptography.SHA1 (Built-in, Allround)
- Streamer.Cryptography.SHA256 (Built-in, Allround)
- Streamer.Cryptography.SHA384 (Built-in, Allround)
- Streamer.Cryptography.SHA512 (Built-in, Allround)
Checksums
- Streamer.Checksums.CRC32 (Custom, Allround)
Utilities
- Streamer.Services.Randomizer (Custom)
Built-in : using .net's own library for this
Custom : using custom written methods for this
Github: https://github.com/TheBarret/Streamer
im still actively working on it, if it happens you see an error or problem, let me know i probably caused it or forgot about something :P
RE: Experimental Encoder - Bypat [Byte Pair Table] - gigajew - Nov 1, 2017
Interesting, good job Barret
RE: Experimental Encoder - Bypat [Byte Pair Table] - Barret - Nov 1, 2017
Updated with a cleaned up version, a lot easier to read and understand now.
RE: Experimental Encoder - Bypat [Byte Pair Table] - 0xDEAD10CC - Nov 1, 2017
It's not a bad idea, but there's tons of this code from my knowledge in C# that could be cleaned up a bit. Lots of boilerplate code and some extensions that I would consider not very useful. Interface names aren't as verbose as they should be "IAlgorithm" - an interface for some kind of algorithm?
Kind of similar to RLE.
RE: Experimental Encoder - Bypat [Byte Pair Table] - Barret - Nov 1, 2017
(Nov 1, 2017 01:39 PM)0xDEAD10CC Wrote: It's not a bad idea, but there's tons of this code from my knowledge in C# that could be cleaned up a bit. Lots of boilerplate code and some extensions that I would consider not very useful. Interface names aren't as verbose as they should be "IAlgorithm" - an interface for some kind of algorithm?
Kind of similar to RLE.
Im no expert, and rle does do similar indeed but its not ment for byte arrays as far as im concerned, RLE was invented for text base transmissions back in the days, think Fax etc etc
i have my own way of doing things, if its better or worse ill leave that beside. :P
RE: Experimental Encoder - Bypat [Byte Pair Table] - 0xDEAD10CC - Nov 1, 2017
(Nov 1, 2017 01:51 PM)Barret Wrote: Im no expert, and rle does do similar indeed but its not ment for byte arrays as far as im concerned, RLE was invented for text base transmissions back in the days, think Fax etc etc
i have my own way of doing things, if its better or worse ill leave that beside. :P
RLE provides an algorithm that could be applied to bytes if you think of the values as integers rather than characters. It's just a running length of the same value that it uses to encode. Instead of characters someone could use 2-value hexadecimal representation of each byte.
RE: Experimental Encoder - Bypat [Byte Pair Table] - Barret - Nov 1, 2017
(Nov 1, 2017 01:55 PM)0xDEAD10CC Wrote: RLE provides an algorithm that could be applied to bytes if you think of the values as integers rather than characters. It's just a running length of the same value that it uses to encode. Instead of characters someone could use 2-value hexadecimal representation of each byte.
Yeah that would be the next variation of that, what im saying is it was originally made for text base transmission