Graham Barr d82da8fd71 Avoid read channel corruption when response size > bufferSize ... When receiving a response, what was happening 1. Read bufferSize and it gets assigned to leftdata 2. Read another bufferSize 3. 2 buffers get appended, but leftdata still points to first buffer 4. Process data buffer which contains only complete responses 5. Back to ReadLoop, but leftdata still points to first incomplete buffer causing corrupt data to be processed Solution is to make leftdata nil once we have merged it with the second buffer		2014-08-18 12:35:31 -05:00
..
client_test.go	a better documents for the client package	2013-12-26 15:28:42 +08:00
client.go	Avoid read channel corruption when response size > bufferSize	2014-08-18 12:35:31 -05:00
common.go	Increase buffer size to 8K	2014-08-18 09:51:33 -05:00
error.go	Use %v instead of %V, which is not a valid Printf verb	2014-03-07 10:21:45 +01:00
id_test.go	Remove depenance on external libs for unique id	2013-08-25 22:49:00 -07:00
id.go	a better documents for the client package	2013-12-26 15:28:42 +08:00
pool_test.go	a better documents for the client package	2013-12-26 15:28:42 +08:00
pool.go	Make pool clients safe for concurrent access with mutex.	2014-05-16 10:23:44 -04:00
request.go	a better documents for the client package	2013-12-26 15:28:42 +08:00
response.go	Use %v instead of %V, which is not a valid Printf verb	2014-03-07 10:21:45 +01:00
status.go	go fmt	2013-08-30 12:36:57 +08:00