added buffering reads and writes to roadmap

Author: illegalprime

ROADMAP.md

@@ -28,3 +28,14 @@ So maybe we should _just_ add `tokio` support, or maybe `mio` is still used and
 
 We need this to pass more autobahn tests!
 
+### Buffer Reads and Writes
+
+In the old crate the stream was split up into a reader and writer stream so you could
+have both a `BufReader` and a `BufWriter` to buffer your operations to gain some speed.
+However is doesn't make sense to split the stream up anymore
+(see [#83](https://github.com/cyderize/rust-websocket/issues/83))
+meaning that we should buffer reads and writes in some other way.
+
+Some work has begun on this, like [#91](https://github.com/cyderize/rust-websocket/pull/91),
+but is this enough? And what about writing?
+

src/client/builder.rs

@@ -231,7 +231,6 @@ impl<'u> ClientBuilder<'u> {
 		self.connect_on(ssl_stream)
 	}
 
-	// TODO: refactor and split apart into two parts, for when evented happens
 	pub fn connect_on<S>(&mut self, mut stream: S) -> WebSocketResult<Client<S>>
 		where S: Stream
 	{
@@ -272,7 +271,7 @@ impl<'u> ClientBuilder<'u> {
 		try!(write!(stream.writer(), "{}\r\n", self.headers));
 
 		// wait for a response
-		// TODO: we should buffer it all, how to set up stream for this?
+		// TODO: some extra data might get lost with this reader, try to avoid #72
 		let response = try!(parse_response(&mut BufReader::new(stream.reader())));
 		let status = StatusCode::from_u16(response.subject.0);
 

src/receiver.rs

@@ -12,7 +12,6 @@ use ws::receiver::{MessageIterator, DataFrameIterator};
 use stream::{AsTcpStream, Stream};
 pub use stream::Shutdown;
 
-// TODO: buffer the readers
 pub struct Reader<R>
 	where R: Read
 {