These are chat archives for GoorMoon/OrientDB-NET.binary

4th
Jan 2015
Peter(Yong) Zhong
@jiujiu1123
Jan 04 2015 09:44
@GoorMoon the I ran into the buffered steam issue today again with 1.7.9 so I slightly mortified one line of code, but I don't like what I did, do you have any other ideas? I changed my original fix that I brought up to this.
My code
        internal Stream GetNetworkStream()
        {
            return new BufferedStream(_networkStream);
        }
Roman Gordon
@GoorMoon
Jan 04 2015 13:36
@jiujiu1123 _networkStream already BufferedStream look here:
https://github.com/orientechnologies/OrientDB-NET.binary/blob/master/src/Orient/Orient.Client/Protocol/Connection.cs#L14
I investigate issue and i think problem is with Memory Storage Type, is return different structure of RECORD_LOAD, RECORD_CREATE
Peter(Yong) Zhong
@jiujiu1123
Jan 04 2015 13:39
I know it is already buffered but it I think what happened is the buffed stream can not do read and write at the same time, but I am not too familiar with the streams so
Roman Gordon
@GoorMoon
Jan 04 2015 13:41
in last commit i added READ_TIMEOUT to the socket and now if have protocol mismatch thrown IOException.
Uploaded to github just now
Peter(Yong) Zhong
@jiujiu1123
Jan 04 2015 13:45
oh, I was just looking over your commits, explains why I didn't find it
Roman Gordon
@GoorMoon
Jan 04 2015 13:46
i just now uploaded it :)
Peter(Yong) Zhong
@jiujiu1123
Jan 04 2015 13:47
I will give it a try, but from what I understand I think this issue is caused by the bufferedstream it self not the tcpsocket, but anyway I could be wrong
Roman Gordon
@GoorMoon
Jan 04 2015 13:54
BufferStream is wait for data, and data is already sent because difference in storage types.