You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because of the mWaitingRequests field of RequestQueue, several Request which have same url and different body, the others request can only be executed after the first Request return. I think this is a little unreasonable, can mWaitingRequests only work for GET method? Common HTTP caches are typically limited to caching responses to GET.
The text was updated successfully, but these errors were encountered:
Why not just call setShouldCache(false) on your requests if you don't want them to be cached? That will bypass mWaitingRequests, and doesn't involve a potentially incorrect assumption that POST requests shouldn't be cached.
Because of the mWaitingRequests field of RequestQueue, several Request which have same url and different body, the others request can only be executed after the first Request return. I think this is a little unreasonable, can mWaitingRequests only work for GET method? Common HTTP caches are typically limited to caching responses to GET.
The text was updated successfully, but these errors were encountered: