-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
URL format for transmission ? #1
Comments
Ah, this seems to work on the desktop client, but can't get it working on the transmission web client, running on a raspberry pi - weird. |
Not sure about the difference between those two clients, but this could have something to do with the fact that pybtracker does not support scraping at the moment. |
Any idea what is needed to implement scraping ? - Would it mean pybttracker serving a webpage, over something like aiohttp ? |
Ah, just read up on scraping a little. .. yep. I know very little about trackers, but am learning. |
UDP trackers work over UDP (to state the obvious) so naturally aiohttp won't help here. Take a look at BEP 15 to find out what needs to be done. Implementation involves something similar to what we're already doing with connect and announce requests. If there's anything in particular you need to know about just comment here and I'll help you as far as I can. |
Here is how I'd probably implement this, if get time - is it possible to sanity check ? A
|
Yes, that's right. |
I had a bit of a look at pytt, it has a really simple looking scraper implementation (also MIT licensed) Having a look back at pybttracker I'm not quite sure how to convert this to using structs as in pybttracker. |
The code you are referring to is for an HTTP tracker which is text based. It won't help you with the UDP tracker which is binary. Did you take a look at BEP 15? It clearly lays out the binary format for you. For example, the scrape request looks something like this:
So creating the request message would look something like: |
This made a lot more sense not being tired :) Cheers for the example. I knocked up a quick patch, any idea how I can test it (I guess creating the request similar to above) + see if its along the right lines ? I tried running the tests in python3.5 and got this:
|
I have no idea. I ran the tests on your fork and all test cases passed cleanly. Do you have any changes you haven't pushed to github? |
Nope, that's it. I guess I need to add some tests of the functionality before this can be merged. |
I've been using rpc to transmission to add the url of the tracker, but it always says
Any idea what the url should look like ?
The text was updated successfully, but these errors were encountered: