These are chat archives for 47deg/fetch

26th
Jul 2016
aappddeevv
@aappddeevv
Jul 26 2016 12:46
I see the notes on supporting existing async clients. Is there some documentation on it? For example, instead of using Query.async(...), I already have a scala Future returned by my client library and would like to easily plugin my "Future" into the Query but I don't know if I should be using sync or async since my client lib is already non-blocking and asynchronous via Future.
aappddeevv
@aappddeevv
Jul 26 2016 17:40
The reason I ask is because if I am generating a future already and am using a Future as my return container, it seems that the underlying creates another promise & future underneath when it runs the query using async().
aappddeevv
@aappddeevv
Jul 26 2016 19:44
Here's a link to write-up of using fetch with dispatch: https://www.gitbook.com/book/aappddeevv/my-dispatch-user-notes/edit#/edit/master/service_composition.md. I am still concerned about too many future/promises being created.