Closed GoogleCodeExporter closed 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:
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
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
Please do it. I couldn't manage it.
Original comment by hepha...@gmail.com
on 19 Mar 2011 at 6:59
Sure, but you don't need them for DC transfer?
Original comment by freezing...@gmail.com
on 19 Mar 2011 at 8:24
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
Original comment by hepha...@gmail.com
on 8 Apr 2011 at 10:10
Original issue reported on code.google.com by
freezing...@gmail.com
on 1 Dec 2010 at 9:59Attachments: