Hello,
in this thread I want to post to you what’s new in 25.5 prerelease plugins. Download here:
monkeybreadsoftware.de/xojo/download/plugin/Prerelease/
or from Dropbox or ask (in private message or email) to be added to the shared dropbox folder.
If you like our plugins, please bookmark, like or forward this thread.
If not, well you can ignore it.
New functions in documentation.
Thanks for supporting our plugins.
If you have questions, please post your question as a new discussion
Greetings
Christian
1 Like
Re the changes to CURLSMultiMBS:
-
Does TransfersRunning differ from the older property RunningTransfers?
-
TransfersCurrent sounds useful. Currently I have to maintain my own dictionary of active transfers, adding an entry whenever I call AddCURL and removing it when the transfer finishes, because RunningTransfers is not a reliable indicator that all transfers have finished. The documentation says
“Returns the number of easy handles currently added to the multi handle.
This does not include already removed handles. It does include internal handles that get added for tasks (like resolving via DoH, for example).”
but it doesn’t elaborate how handles are removed. Is this an automatic internal mechanism, and can I rely on the new TransfersCurrent property to tell me that all added CURLS have finished one way or another?
The old property is what CURL reports from Perform on how many transfers are running.
the new functions query the internal lists from CURL. And CURL has a lists for:
- current → xfers: transfers added to this multi. Each transfer’s mid may be present in at most one of these
- running → process: transfer being processed
- pending: transfers in waiting (conn limit etc.)
- done → msgsent: transfers done with message for application
Thanks. So does TransfersCurrent = 0 reliably tell me that all CURLS added have finished?
Yes, of course. Then also the TransfersFinished event should fire.