thanks michael i got it, its ok i think i will figure out a way around if i can in windows
will this be updated on libtorrent in later versions or it needs a workaround by the programmer who uses it ?
________________________________
From: Michael Mckeown <***@outlook.com>
Sent: Monday, May 8, 2017 2:24:43 PM
To: General discussion about libtorrent
Subject: Re: [libtorrent] Advice on some options needed
No you use what's best for the server, one supports a smart client and
the other a smart server, I was just letting you know about the bug
before testing as the bug is such that on windows anyway you need to
hold the power button down to restart the pc as the system becomes
unresponsive.
On 08/05/2017 12:17, Nocs ... wrote:
> Thank you Michael,
>
>
> So users is best to use only url_seeds when they create a torrent file.
>
> Where could anyone check if the http_seed is not broken and can be used later on if they will be updated ofcourse
>
> <http://aka.ms/weboutlook>
>
> ________________________________
> From: Michael Mckeown <***@outlook.com>
> Sent: Monday, May 8, 2017 1:16:22 PM
> To: General discussion about libtorrent
> Subject: Re: [libtorrent] Advice on some options needed
>
> You can use both at the same time but http_seed is broken so you need to
> remove any of these when you add a torrent or when you get metadata from
> a magnet link and don't add any when creating torrents.
>
> ie, on metadata_received_alert/add_torrent_alert
>
>> std::set<std::string> h = handle.http_seeds();
>> for ( auto u : h ) {
>> handle.remove_http_seed(u);
>> }
> example torrents using http_seeds: https://www.debian.org/CD/torrent-cd/
>
> example torrents using url_seeds: https://www.gimp.org/downloads/
>
>
> On 08/05/2017 10:49, Nocs ... wrote:
>> Thanks for the reply and the infos,
>>
>> about the add_url_seed() and add_http_seed() i cant find anywhere if a user can use both of them at the same torrent file he creates
>>
>> is this possible or a user choose only one of the two types ?
>>
>>
>> <http://aka.ms/weboutlook>
>>
>> ________________________________
>> From: Calum Lind <***@gmail.com>
>> Sent: Monday, May 8, 2017 12:26:54 PM
>> To: General discussion about libtorrent
>> Subject: Re: [libtorrent] Advice on some options needed
>>
>> On 8 May 2017 at 06:36, Nocs ... <***@hotmail.com> wrote:
>>
>>> Hello again ^.^ i am very happy that libtorrent finally works fine and i
>>> am making my first test client with its functions.
>>>
>>> I have some theory questions though about some option that i dont
>>> understand and never experienced in torrents.
>>>
>>> 1. is about add_url_seed() and add_http_seed()
>>>
>>> I understand what they are but as options can anyone use both of them at
>>> the same time or have to choose one of them only while he creates a new
>>> torrent file ?
>>>
>>> the add url seed its in the examples and i guess is the ones mostly used
>>> but what shouldl one enter as http seed ? is it the same ? entering an http
>>> url instead of udp one ?
>>>
>> Detailed in documentation:
>>
>> http://libtorrent.org/single-page-ref.html#torrent_handle
>> http://libtorrent.org/manual-ref.html#http-seeding
>>
>>
>>
>>> 2. is about set_hash() and set_file_hash()
>>>
>>> In the examples of libtorrent is using the set_piece_hashes() instead of
>>> any of the above functions.
>>> Where could a user use any of the above as options ? I mean that should i
>>> use only for the client users the set_piece_hashes() as in the examples of
>>> libtorrent or should i give an option of any of the other two also cause i
>>> dont really know what and why they are used for so i can understand if they
>>> are needed to users as options.
>>>
>>> Can someone need to use both of them, can someone need one of them or just
>>> should i use only the set_piece_hashes() ?
>>>
>> I think if you need to ask then just use set_piece_hashes
>>
>>
>>> 3. is about set_priv()
>>>
>>> I never experienced a private torrent seed or feed and i dont fully
>>> understand it so i can use it as option.
>>>
>>> Its easy as it seems to be used it is just a boolean of if the user want
>>> his torrent file to be private or public
>>>
>>> Do i have to set anything else while using it as option or is just a
>>> boolean set inside the creation of torrent file ?
>>>
>>>
>> This is a private torrent flag which stops torrent using DHT. Note that it
>> will affect the torrent info hash. Lots of info on google:
>> http://wiki.bitcomet.com/private_torrents
>>
>>
>>> I only need some theoritical answer so i can understand the way the above
>>> works nothing too detailed
>>>
>>> just to be informed and use them or not as options inside my client for
>>> the users
>>>
>>> Thank you in advance
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Libtorrent-discuss mailing list
>>> Libtorrent-***@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/libtorrent-discuss
>>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Libtorrent-discuss mailing list
>> Libtorrent-***@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/libtorrent-discuss
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Libtorrent-discuss mailing list
>> Libtorrent-***@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/libtorrent-discuss
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Libtorrent-discuss mailing list
> Libtorrent-***@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/libtorrent-discuss
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Libtorrent-discuss mailing list
> Libtorrent-***@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/libtorrent-discuss
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Libtorrent-discuss mailing list
Libtorrent-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libtorrent-discuss