![]() I am not totally sure what you meant by "It assumes that only one of them can be used on the command line, but what's the point?" though, can you please elaborate? ![]() It assumes that only one of them can be used on the command line, but what's the point? The second option (with separate parameters) seems to me a bad idea. ![]() And here the question arises (at least for me), whether all available infohashes are required for use by external scripts, and if so, in what form they should be provided - in a single parameter (for example, infohash1, infohash2), or in separate parameters. "Run program on torrent complete" feature). The second is providing parameters for running an external program (i.e. So, there is no problem here to provide all the available torrent info hashes. The first is the providing information to the user through some kind of UI (WebAPI also applies here). There are two main aspects that depend on infohashes that we are talking about. Mostly devs or script users are expected to weigh in here.Īlso I notify doesn't seem to be enough clarity here. I'll let them present them in the comments. Just add another field in the GUI/WEBUI.įor number 2 and had some proposals.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |