Token Refresh about networking HOT 6 CLOSED

HiI! Right now we only have "unauthorizedRequestCallback", it gets called when a 403 is triggered so you can renew your token.

https://github.com/3lvis/Networking/blob/master/Sources/Networking.swift#L169

I think we could do better, though. What are your thoughts on the current solution?

from networking.

🤔 Is it called for all requests? If so, In theory, you could put in a couple of NSLocks and initiate retrials for all the requests after getting a new token, right?

from networking.

That could work 🤔.

I guess that's the biggest missing piece at the moment, the retrials after the token part. I guess ideally you have all the requests in a queue and if you get a 403, you stop all the requests in the queue until the token is renewed, then you restart the pending requests.

from networking.

all the requests in a queue

You mean in a concurrent queue, correct? Doesn't URLSession do that by default?

from networking.

We could probably use that one

https://developer.apple.com/documentation/foundation/urlsession/1411597-init

from networking.

@3lvis how about we have a post and a pre-response hook for all requests? That way, you don't execute a completion block (like in https://github.com/3lvis/Networking/blob/master/Sources/Networking%2BHTTPRequests.swift#L13 )

until the post commit hook is completed. If you have a 401 with an expired token, execute a lock.lock*(), and refresh your tokens. Once your token is refreshed, retry the request (not quite sure how you'd do that)

I've also been considering implementing this an Rx extension to Networking (imagine having a shared observable and every request using the retry operator with it. It could also be used in conjunction with Rx's smart retry policies

from networking.