On Fri, May 6, 2016 at 9:29 AM, Lance Dillon wrote:
> Hmm, probably a typo, documentation says composited-changed for both gtk2
> and 3. Looks like it may have existed since 2.10. I think it probably
> hasn't been tested. There are a lot of signals that would be hard to test
> without a complex
Hmm, probably a typo, documentation says composited-changed for both gtk2 and
3. Looks like it may have existed since 2.10. I think it probably hasn't been
tested. There are a lot of signals that would be hard to test without a
complex test.
Sent from Yahoo Mail on Android
On Thu, May 5
Should any of the following have a CHANGES note?:
* ADT.Heap: Added low_peek().
* Fix GTK2.SourceBuffer undo/redo signal names
* Fix spelling of composite[d]_changed signal
- Is that an API change or where the signals not properly hooked up
before?
* Crypto/SSL
- There is a ton of Crypt
You might want to look into HTTP.Session, since that will handle
things like reuse of connections and cookies. (I'm not saying it's
intuitive, but it might be a better endpoint than Query for a
Concurrent solution.)
(Query was never written not to have a layer on top of it.)
Hi guys!
I started experimenting with the new Concurrent.Promise/Concurrent.Future
classes and implementing a HTTP client module using the promise/future stuff.
The reason for this is that the async stuff in Protocols.HTTP.Query is far from
intuitive. With promises/futures I think you get a sup
