Partial file upload protocol
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| StrongDC++ |
New
|
Undecided
|
Unassigned | ||
Bug Description
My client is 2.30, other client is 2.22
I am a distributed hub writer/
When I am uploading a file to a single user (the downloading user is most definatly downloading from more than 1 source but this might be irrelevent)
I get the following line trace
Hub: [Incoming]
Client: [Outgoing][<snip>] CSUP ADBAS0 ADBASE ADTIGR ADBZIP ADZLIG
Client: [Outgoing][<snip>] CSTA 000 RFadc:/
Client: [Incoming][<snip>] CSUP ADBAS0 ADBASE ADTIGR ADBZIP ADZLIG
Client: [Outgoing][<snip>] CINF ID<snip> TO3078468531
Client: [Incoming][<snip>] CINF ID<snip>
Client: [Incoming][<snip>] CGET file TTH/SMU5G2NS5QS
Client: [Outgoing][<snip>] CSND file TTH/SMU5G2NS5QS
//Few seconds later
Hub: [Incoming]
Client: [Outgoing][<snip>] CSUP ADBAS0 ADBASE ADTIGR ADBZIP ADZLIG
Client: [Outgoing][<snip>] CSTA 000 RFadc:/
Client: [Incoming][<snip>] CSUP ADBAS0 ADBASE ADTIGR ADBZIP ADZLIG
Client: [Outgoing][<snip>] CINF ID<snip> TO3078468531
Client: [Incoming][<snip>] CINF ID<snip>
Client: [Incoming][<snip>] CGET file TTH/SMU5G2NS5QS
Client: [Outgoing][<snip>] CSND file TTH/SMU5G2NS5QS
//Few seconds later
Hub: [Incoming]
Client: [Outgoing][<snip>] CSUP ADBAS0 ADBASE ADTIGR ADBZIP ADZLIG
Client: [Outgoing][<snip>] CSTA 000 RFadc:/
Client: [Incoming][<snip>] CSUP ADBAS0 ADBASE ADTIGR ADBZIP ADZLIG
Client: [Outgoing][<snip>] CINF ID<snip> TO3078468531
Client: [Incoming][<snip>] CINF ID<snip>
Client: [Incoming][<snip>] CGET file TTH/SMU5G2NS5QS
Client: [Outgoing][<snip>] CSND file TTH/SMU5G2NS5QS
Given that the Client-Client connection is already open, why is the downloading client resending a CTM request and re-negociating all the SUP and INF data for each segment it is downloading from me? I would argue that it is irrelevent and unneeded as the connection is never being terminated before the next DCTM is sent.
| Big Muscle (bigmuscle) wrote | #1 |
This looks more that some kind of error occurred or the connection was shut down by some reason. It would explain why it always requested the same segment.