Transmission

thank you for your reply, very appreciate
the flow of calling transmission api is same as cli(aommand line)
but instead of calling tr_torrentStart() ; we call tr_torrentStop,
and up to user to choose start then call tr_torrentStart()

quote "That (stop response) should be followed by a start ...

Hi everyone
I'm porting transmission on an embedded system
and I am stuck on announce to tracker; when I announce to tracker(add torrent and stop torrent) I get tracker response as following

Got announce response: connected:1 timeout:0 seeders:1586 leechers:385 downloads:-1 interval:1800 min ...

My question is for each new task(add torrent) created; should I init a new session < call tr_sessionInit( )> ?
and when task is deleted , should I call sessionClose()?
or there is only one session inited and I should use

tr_torrent * tr_torrentNew( const tr_ctor * ctor, int * setmeError );
to ...

Put it in another way, dose transmission require a multi-threaded libevent lib? Or
a single thread libevent can work with Transmission fine , just like I mentioned above
adding a task means creating a libevent thread, does that mean I need a multi-threaded
libevent lib?
thanks in advance

Hi everyone I am a newbie in Transmisson,
I read that the tr_sessionInit() is called when I add a new task
(BT task); and when I delete the BT task tr_sessionClose()
should be called. That means every task will create a libevent
thread and a Web thread when we call tr_sessionInit().
Am I correct ...