Hi George,

Lets talk about signals

Is there any need for more Signals than Starting, Stopping, and Error? (given they all pass a code / reason)

The reason I ask is the current signals are somewhat confusing, and don't really cover enough situations to be effective. It would also seem to be easier to code KT itself if there aren't a random number of special case signals instead of a static set with well defined codes.

Here's a first pass at the reason list for each.

Start: Allocating data, Start Downloading, Start Seeding, Torrent added, Unpaused

Stop: Finished Downloading, QM timer stopped, Torrent removed, Maximum share ratio reached, Maximum seed time reached, Paused,

Error: File does not exist, Low disk space, Out of disk space, Corrupted data,

And possible an "Other" if you don't want to place things like pause, un-pause, removed, etc. in Start and Stop.

Needs all the rest, and the above to be reworded and codified, but...

Thoughts?,
Sam

Sam wrote:Hi George,

Lets talk about signals

Is there any need for more Signals than Starting, Stopping, and Error? (given they all pass a code / reason)

The reason I ask is the current signals are somewhat confusing, and don't really cover enough situations to be effective. It would also seem to be easier to code KT itself if there aren't a random number of special case signals instead of a static set with well defined codes.

Here's a first pass at the reason list for each.

Start: Allocating data, Start Downloading, Start Seeding, Torrent added, Unpaused

Stop: Finished Downloading, QM timer stopped, Torrent removed, Maximum share ratio reached, Maximum seed time reached, Paused,

Error: File does not exist, Low disk space, Out of disk space, Corrupted data,

And possible an "Other" if you don't want to place things like pause, un-pause, removed, etc. in Start and Stop.

Needs all the rest, and the above to be reworded and codified, but...

Thoughts?,
Sam

I also think so.