Re: Problems using API (Switch)
Posted: April 18th, 2012, 12:22 am
The thinf is, when you're pushing 100 files, to diffent users at the same time, the quicker you connect, and disconnect the better, and more quickly you get through the queue.
That's why I am using addfile, just sending a URL and disconnecting, and letting the remote SABnzbd download the NZB file at their leisure, through my HTTP interface, which is much more capable of handling lots of simultaneous threads.
That's why I asked for multiple addfile, so I don't have make 5 different connections in succesion to a users SABnzbd to push their queued files, just one connection, a list of urls and categories, and done with it.
Right now I am managing the load of uploading URLs, but I only have a couple of hundred active users, so I am thinking ahead, as ways to uploading multiple URLs and cats, with only one connection. I love SABnzbs, and love that I have hundreds of users using it too, and I want to make everything more efficient for them. So they know I can push them a NZB file quickly, and not have a bottleneck on my side.
The remote xcat for each file would not be needed, if when SABnzbd fetches the NZB the "X-DNZB-Category" header is run through the users filters, and checked for wildcards as well. (right now it's being ignored as well).
If I just upload the files,
That's why I am using addfile, just sending a URL and disconnecting, and letting the remote SABnzbd download the NZB file at their leisure, through my HTTP interface, which is much more capable of handling lots of simultaneous threads.
That's why I asked for multiple addfile, so I don't have make 5 different connections in succesion to a users SABnzbd to push their queued files, just one connection, a list of urls and categories, and done with it.
Right now I am managing the load of uploading URLs, but I only have a couple of hundred active users, so I am thinking ahead, as ways to uploading multiple URLs and cats, with only one connection. I love SABnzbs, and love that I have hundreds of users using it too, and I want to make everything more efficient for them. So they know I can push them a NZB file quickly, and not have a bottleneck on my side.
The remote xcat for each file would not be needed, if when SABnzbd fetches the NZB the "X-DNZB-Category" header is run through the users filters, and checked for wildcards as well. (right now it's being ignored as well).
If I just upload the files,