search

kythyria / msnp-sharp

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

4.0 Can't send emotiocn after getting the remote user's diplayimage #241

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
0. Delete the mcl files.
1. Login using example client 4.0
2. remote user use WLM2011
3. Try to transfer a custom emoticon to remote user. 

What is the expected output? What do you see instead?
remote user can see the custom emoticon.

Please use labels and text to provide additional information.
Please the trace log attached.

Original issue reported on code.google.com by freezing...@gmail.com on 1 Dec 2010 at 9:59

Attachments:

GoogleCodeExporter commented 9 years ago 
Now even the first time not works. Look at the trace log.

Original comment by freezing...@gmail.com on 10 Dec 2010 at 2:58

Attachments:

GoogleCodeExporter commented 9 years ago 
I found the problem... Please have a look these variables. I cannot track these 
variables. Please have a look and redesign...

P2PBridge:

syncIdentifier
localTrackerId
packageNumber

P2PSession:

localBaseIdentifier
localIdentifier
remoteBaseIdentifier
remoteIdentifier

Original comment by hepha...@gmail.com on 19 Mar 2011 at 8:44

GoogleCodeExporter commented 9 years ago 
The **BaseIdentifier is the initial sequence number (we call it Identifier) 
that used for the transfer. If you don't feel these variables useful in the new 
p2p design, just feel free to remove them :), just make sure everything work.

Original comment by freezing...@gmail.com on 19 Mar 2011 at 6:13

GoogleCodeExporter commented 9 years ago 
Please do it. I couldn't manage it.

Original comment by hepha...@gmail.com on 19 Mar 2011 at 6:59

GoogleCodeExporter commented 9 years ago 
Sure, but you don't need them for DC transfer?

Original comment by freezing...@gmail.com on 19 Mar 2011 at 8:24

GoogleCodeExporter commented 9 years ago 
DC must be synced only once. If you lost localTrackerId dc bridge will die.
For DC bridge we need only localTrackerId. All of session identifiers can be 
deleted.

But in SDG bridge, it acts as SBBridge for old clients < msn21. So, when you 
send invite message, it must be sent with sync+rak operation code for each 
transfer.
SDG bridge must have localTrackerId for each transfer. So I couldn't manage 
track identifier.

4.0 can be released after this bug fixed.

Original comment by hepha...@gmail.com on 20 Mar 2011 at 10:23

GoogleCodeExporter commented 9 years ago

Original comment by hepha...@gmail.com on 8 Apr 2011 at 10:10