BitTorrent implementation - what next?

Hi Peter,

because you have the best overview over the whole project, I’d like to ask you what could I do as a next step. I’ve browsed through the specifications and these are my ideas what could I implement (maybe we should create tickets for them):

  • creating (converting) tracker GET requests into QByteArray (class TrackerRequest) - specs
  • tracker responses parsing (class TrackerResponse and TrackerResponseParser) - specs
  • peer wire protocol (no clear idea yet) - specs

I see that there is something already done in Protocols/BitTorrent/Packets and Protocols/BitTorrent/Transport (it’s just a sketch there I suppose) but I haven’t studied it that deep.

Another question is whether I should merge your whole development branch with mine (or you mine - or should I just continue to work in “your” branch where there are no Torrent and TorrentParser classes yet?), because we have changed Packet design so maybe it would be good if I have the same version. What do you think?

I’d be very grateful for any hints or comments from you!

Thanks in advance,

Petr

Would you like to post a relpy?


This post starts a thread.
Follow-ups:
Re: BitTorrent implementation - what next?
Hi Petr, - creating (converting) tracker GET requests into QByteArray (class TrackerRequest) - specs Maybe you could try creating a TrackerRequestSession? You pass it the announce URL and the TrackerReqeust. TrackerRequestSession then (more...)