It would make sense though to have the core of Fuel to be synchronous. As far as I know
URLConnection
does not support any real asynchronous operation and thus will always use a Thread for any network operations. The asynchronous part can be build on top of that so the current API can remain the same.