search

kythyria / msnp-sharp

Automatically exported from code.google.com/p/msnp-sharp
0 stars 0 forks source link

This stream does not support seek operations. #214

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Sign on msnp-sharp
2.After about ten minutes to change personal message
3.error

What is the expected output? What do you see instead?
Exception in SingleSignOn.cs,line 674

Exception message: 
This stream does not support seek operations. See innerexception for detail.

What version of the product are you using? (MSNPSharp, OS, Mono etc.)
3.1.2 Beta

Please provide any additional information below:

Original issue reported on code.google.com by jarvis.chen66@gmail.com on 23 Aug 2010 at 1:51

GoogleCodeExporter commented 9 years ago 
Hello,

First, please check out the DEV version in the trunk to whether this issue 
still exsits. 312beta is no more supported.

Original comment by freezing...@gmail.com on 24 Aug 2010 at 5:41

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
After checked out the the DEV version in the trunk, this issue is still can be 
reproduced in this version.

Original comment by jarvis.chen66@gmail.com on 25 Aug 2010 at 2:39

GoogleCodeExporter commented 9 years ago 
Are you testing with the example client or your own code? In example client, it 
seems that I can't reproduce the issue. Can you give me more details?

Original comment by freezing...@gmail.com on 28 Aug 2010 at 1:40

GoogleCodeExporter commented 9 years ago 
File: SecurityTokenServiceWrapper.cs
Function: GetReaderForMessage()
Line: 51, 57, 60, 65, 68,

Error: NetworkStream does not support seek operations

Affects: 3.0.2.1650 and DEV

Solution: Define a MemoryStream as innerStream, then write networkstream to 
memorystream. See 2.5. stable (MSNSecurityServiceSoapClient)

Original comment by hepha...@gmail.com on 28 Aug 2010 at 1:46

GoogleCodeExporter commented 9 years ago 
Oh man, it's really happy to see you are still here! You are doing code review, 
haha.

I have a different opinion, if that stream can not seek, that means some error 
just occurred. So what I need to do is check message.Stream.CanSeek, if false, 
return base.GetReaderForMessage. What do you think?

Original comment by freezing...@gmail.com on 28 Aug 2010 at 6:01

GoogleCodeExporter commented 9 years ago 
Actually, I know this can be solved by using a FakeStream, but I want to figure 
out why the response will come out with a ConnectionStream, I think that's 
because it's time out.

Original comment by freezing...@gmail.com on 28 Aug 2010 at 6:47

GoogleCodeExporter commented 9 years ago 
Hi,

Just check out the latest DEV version and verify whether the issue still exists.

Original comment by freezing...@gmail.com on 29 Aug 2010 at 11:38

GoogleCodeExporter commented 9 years ago 
This issue is solved,thank you.

Original comment by jarvis.chen66@gmail.com on 30 Aug 2010 at 8:35

GoogleCodeExporter commented 9 years ago

Original comment by freezing...@gmail.com on 30 Aug 2010 at 8:04