Re: [Wt-interest] condition_variables and Wt

Hello Aarón, Wt::Http::Client should indeed not use the WApplication's WIOService and post every event to the current session if a different WIOService has been specified. That's been fixed now, so using a different WIOService should work now. Thanks for calling that to our attention. However,

Re: [Wt-interest] condition_variables and Wt

I had tested with different "approaches", even with my own IOService, passed as parameter to Wt::Http::Client with 2 and 3 threads. The thing is: - If Http::Client sees the current thread owns a WApplication object (if the thread is binded to the WApplication), it ignores the passed

Re: [Wt-interest] condition_variables and Wt

On Sat, Sep 24, 2016 at 2:31 AM, Aarón Bueno Villares wrote: > I've tried to make a "synchronous" recaptcha verification using the > underlaying Wt's IOService, asynchronous in nature. The code is the > following one: > > // response_ready is just a std::condition_variable (I