On Fri, Feb 01, 2013 at 04:31:36PM -0500, Summers Pittman wrote:
So RestAdapter right not has to be used from the UI thread (an
Activity or Fragment) otherwise the callback may not be called. More
specifically, the callback provided to read, save, etc is only called
on the UI thread of the application. This makes it really easy to put
UI code in the callback, but the side effect is if the UI thread is
blocked or not running then the callback won't get fired.
I don't think this is a huge problem for 1.0 (assuming we document
it), but I would like to get it fixed sooner rather than later.
How much time would this take to be fixed? I think this is something
that needs to be fixed before 1.0 if possible...
The easiest was to fix it would be to attach a handle to a Thread
(via
a Handler, Looper, or Thread) to PipeConfig that is passed to the
RestAdapter. If one isn't provided we can keep the same behavior we
have now otherwise we can use the provided thread.
How the other client libraries
address it? Is this a no-brainer for "the
average android dev"?
-- qmx