On Thu, 25 May 2017, Lucas Pardue wrote:

>> Another approach would be to offer a callback for state changes so that
>> applications can get told when the transfer state changes and then they
>> could do whatever they want

> With my Statechart hat on, it sounds like you're proposing triggering "new"
> events on state entry. That does indeed sound better than polling but I
> wonder if a simpler approach might just be to emit the "old" events that
> triggered the libcurl state transition.

Either way, I was hoping for someone to step forward and say that getting this
information (using any of the said means) sounds like something they'd like to
see and would then provide an excellent explantion for us as to why this makes
libcurl much better.

So far, I think the provided rationales for us adding this feature haven't
been strong enough to counter the risks and possible future agonies.

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:   https://curl.haxx.se/mail/etiquette.html