#4525 closed Enhancement (invalid)
'torrent id' should be cached
| Reported by: | reardon | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | None Set |
| Component: | Transmission | Version: | 2.33 |
| Severity: | Normal | Keywords: | |
| Cc: |
Description
the 'torrent id' response to an announce should be cached, saved in .resume, and reloaded on startup.
I haven't looked exhaustively, but I haven't seen an argument against treating the 'torrent id' response as a long-lived value.
The benefit will be mostly with private trackers that use this as a means of tracking. I know of at least two trackers that appear to use this as a means of limiting clients to one instance/location.
Change History (2)
comment:1 Changed 11 years ago by jordan
- Resolution set to invalid
- Status changed from new to closed
- Type changed from Bug to Enhancement
comment:2 Changed 11 years ago by reardon
My brain didn't work. Of course I meant 'tracker id' not 'torrent id'. Doh. Will file a new bug.
Note: See
TracTickets for help on using
tickets.
I don't see any way for trackers to possibly use it. The torrent-id is only used inside of Transmission; it's not in the announces or scrapes and is never shared with trackers.