Implementing IO Stream in VB/C#

Question

Hi,

I was wondering if someone would be able to to give me a bit of an crash course on implementing the "IO.Stream" class with their override properties and statement(s). I mean that I under stand how the IO stream itself works. But the part of taking data from the source stream, then doing thing with the data before writing the data to its base stream is the part that I quite understand fully. For the sake of an example, both Compression and Decompression IO stream(s) for how they work their inner workings with the data would be the best way that I can explain for that I'm trying to understand.

In the example case of Compression and Decompression IO streams to my understanding that both of their streams are both "One-Way" streams that I'm aware of. And that's all fine and dandy and able to work with that. But with doing things like "Two-Way" IO streaming from the same base stream "Without" closing the base stream is the part that I just don't quite follow for the way that works like in Network stream. "ex., Compress the data before sending on the network stream. Then decompressing that data on the receiving network stream. Then doing the process in reverse on the same stream." Even encryption streams is another example for what I'm trying to explain and trying to understand for when it comes to how IO streams function.

So if anyone is able provide me with ether some well laid out block diagrams, or some kind of source code example(s) with proper documentation, would be awesome. I can work with C# source code example(s) if needed, but I would rather prefer VB source code example(s) instead. Or at least well documented block diagram(s) and/or example(s) the explains in enough detail for how to implement the "IO.Stream" class because the way that the MSDN is laid out these days tends to make things more head scratching for me then it really needs too be.

Thank you for your time...

GEMWare

P.S. to the MSDN Development Team...

If all possible as a request. Could you pass this message to the "Higher-Up(s)" to fix and cleanup the MSDN .Net Framework Documentation Library where the source code example(s) is more properly displayed and not glitched. And also for any object(s) and/or control class(s) inherited base statements is at least ether Hidden or Collapsed if not removed from what is relevant to a given control or object. And plus to add better explanation for using object(s) and their given statement(s) for were they are better lade out and more readable.

Because depending on what a person is trying to look for and learn. That there would ether be "Way" too much information, or "No" useful information at all to the point of no purpose of a given link to click on. I mean that a person reading a given page has to be psychic for what little that is explain. Properties references seems to be the worst for this from what I've see. Its to the point of ether someone forgot to add the documentation for one reason or another, or that someone got promoted from useless to jobless and that no one took over.