StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14335285
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-15T10:06:31.293
FavoriteCount
0
LastActivityDate
2013-01-15T10:06:31.293
LastEditDate
LastEditorUserId
0
OwnerUserId
1444766
ParentId
14329517
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
The relevant documentation about the libtorrent part is here: <a href="http://www.rasterbar.com/products/libtorrent/manual.html#http-seeding" rel="nofollow">http://www.rasterbar.com/products/libtorrent/manual.html#http-seeding</a> and the specs are <a href="http://bittorrent.org/beps/bep_0019.html" rel="nofollow">http://bittorrent.org/beps/bep_0019.html</a> and <a href="http://bittorrent.org/beps/bep_0017.html" rel="nofollow">http://bittorrent.org/beps/bep_0017.html</a> (both being supported by libtorrent, as "url seeds" and "http seeds"). IIRC, BEP19 (webseeds, or urlseeds) is rather straight-forward from the server POV, and you don't need to do anything special there - you just serve the files as you would do for a normal HTTP requests for that file (so, the second part of your question doesn't quite make sense here). With BEP17, you rather use a unique http endpoint, and pass it get parameters to specify what the client wants (which for example allows for better throttling control and range selection) (eg: <a href="http://example.com/seed/?info_hash=X&piece=Y&ranges=Z" rel="nofollow">http://example.com/seed/?info_hash=X&piece=Y&ranges=Z</a>). This second approach is more flexible if you intend to have more (programmatic) control over what is downloaded, but obviously requires a lot more code to write to handle the requests though. Again, from the server POV, this is not that different from regular HTTP transactions, and there is nothing special about "seeding" here. You just serve files (each with its own url, either directly, or via a handler). A for the metadata part, with BEP19, you add a "url-list" extension (with the full url of your file: <a href="http://example.com/seeds/SOMEFILE.txt" rel="nofollow">http://example.com/seeds/SOMEFILE.txt</a> - watch out for multi-file torrents), whereas BEP17 uses the key "httpseeds" (with your endpoint, eg: <a href="http://example.com/seed/" rel="nofollow">http://example.com/seed/</a>). Depending on whether your Jetty also handle metadata generation or not, you might prefer BEP19 over BEP17, for your urls to be more predictable / the metadata generation to be simpler... Hope that helps.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSelective downloading of torrents via webseeding
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMangled Deutz
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.