Opened 7 years ago

Last modified 7 years ago

#4144 new Enhancement

Support for BEP 17 (Client-Side Support for Script Controlled HTTP Seeding)

Reported by: dak180 Owned by: jordan
Priority: Normal Milestone: None Set
Component: libtransmission Version:
Severity: Normal Keywords:
Cc:

Description

This would be very useful to me (and anyone else that wishes to run web-seed backed tracker with fine grained controls) as someone who runs such a tracker (all torrents on the tracker are legal and thus suited to test against).

Additionally I have hosted a copy of the example scripts for the server side implementation if you wish to test additional configurations.

If there is anything I can do to help to get BEP 17 implemented (I am, however, not a C coder) please let me know.

Change History (3)

comment:1 Changed 7 years ago by jordan

I'm not sure that I see the advantage to this over BEP 19 (webseeds / getright), which we alerady support.

In this thread the two are discussed, and I don't see anything very compelling for BEP 17 yet.

comment:2 follow-up: Changed 7 years ago by jordan

What kind of fine-grained controls are you referring to that could be done with BEP 17 but not BEP 19?

comment:3 in reply to: ↑ 2 Changed 7 years ago by dak180

Replying to jordan:

What kind of fine-grained controls are you referring to that could be done with BEP 17 but not BEP 19?

A good example would be if you wanted to restrict bandwidth and/or simultaneous downloads without having to mess with the server configuration, which depending on how you are hosted you may not be able to do.

It also allows you to make it so that the files cannot be downloaded without having to go through the script to avoid overloading the server.

Additionally it works much better for multi-file torrents as a client need only request a piece (or part of a piece) from the script and not have to worry about if the piece crosses file boundaries.

Note: See TracTickets for help on using tickets.