Closed GoogleCodeExporter closed 9 years ago
Well 2.0 handles things a bit differently. There's only a bytesTransfered
field; progress is calculated if PircBotX knows the final size of the file. You
shouldn't have any concurrency issues since your only reading a value, not
writing to it.
Instead of bringing back packetDelay which might not fit your needs I've added
a callback method onAfterSend() to the FileTransfer abstract class. You can
implement your own delay algorithm without having to hack around a single delay
field or synchronization nonsense. Just remember you have to create your
subclass in BotFactory so PircBotX uses the correct one.
Added in Revision 14ee2104f6be
Original comment by Lord.Qua...@gmail.com
on 15 Oct 2013 at 2:04
Original issue reported on code.google.com by
jely.chr...@gmail.com
on 1 Oct 2013 at 8:38