Mod/map downloader and lobby integration - Page 3

Mod/map downloader and lobby integration

Discuss the source code and development of Spring Engine in general from a technical point of view. Patches go here too.

Moderator: Moderators

User avatar
AF
AI Developer
Posts: 20687
Joined: 14 Sep 2004, 11:32

Re: Mod/map downloader and lobby integration

Post by AF »

hmm I did say that I was implementing my won as a test and wanted to use your client as my own code was unlikely tog et anyway, and indeed it didnt get anywhere.

You also forgot satiriks post.
User avatar
Licho
Zero-K Developer
Posts: 3803
Joined: 19 May 2006, 19:13

Re: Mod/map downloader and lobby integration

Post by Licho »

Im adding 2 backup trackers:

tracker2.caspring.org, backup-tracker.licho.eu

tracker2 will run permanently (when I establish it), backup-tracker will most likely be just my PC in case both fail.

Also adding site with protocol description:
http://www.caspring.org/wiki/DownloaderProtocol
Ifein
Posts: 56
Joined: 23 Mar 2006, 00:44

Re: Mod/map downloader and lobby integration

Post by Ifein »

Licho wrote:Ifein:
the S- on startup are sent, because if client loses connection to coordinator, it keeps seeding (to not break existing downloads, p2p works well even if server randomly crashes).
So on startup server tries to "synchronize" clients by sending them full lis of S-.
A disconnected client keeps seeding, when reconnecting the servers tells him to stop. Why? There can still be leeching clients, so the client should decide when to stop or not.
When you are sending S- for all torrents, why just don't send S- and the client resets itself? Except for running downloads...
Licho wrote: The S+, S- in quick succession [...]
Both of these later problems wont happen when I implement full http seeding.
"full http seeding" ? No more torrent downloads?
Torrent downloads would still cause this problem.
User avatar
Licho
Zero-K Developer
Posts: 3803
Joined: 19 May 2006, 19:13

Re: Mod/map downloader and lobby integration

Post by Licho »

Tracker send S- if there are no more clients requesting that torrent.
It doesnt send S- for every torrent when client connects but only for those not needed.

Client cannot decide reliably because of way how torrent works. Number of seeds and peers is not reliable at all and is refreshed at best once per minute.

Full http seeding means http will work just like another torrent peer. Right now downloader stopped torrent and used normal http download instead - this is what caused S+/S-.
Post Reply

Return to “Engine”