5

I have a project which you can imagine is like the Facebook app and I'm having trouble grasping how to organize it with RestKit and handle tokens since I'm a RestKit beginner.

This is what I got so far:

  • Core Data NSManagedObject classes, for each of them I added a category called REST that has functions to provide RKObjectMapping and RKRouteSet
  • custom RKObjectManager subclass which handles setting up headers, MIME types, setting authorization headers and Core Data stores
  • RKObjectRequestOperation subclass

If you have organizational advice shoot, but my main question is how do I implement automatic token refreshing after recieving a 401 HTTP status code and firing the failed request again with a fresh token?

I started by overriding the metod in my RKObjectRequestOperation subclass:

- (void)setCompletionBlockWithSuccess:(void ( ^ ) ( RKObjectRequestOperation *operation , RKMappingResult *mappingResult ))success failure:(void ( ^ ) ( RKObjectRequestOperation *operation , NSError *error ))failure

So now I can intercept a 401 response, but now I have to make another call to refresh the token and then re-enqueue the failed operation with a fresh token, please advise how to do that.

Sasha_K
  • 53
  • 3

1 Answers1

3

I generally wouldn't use a custom RKObjectRequestOperation if you are using an object manager. I'd handle it at the object manager level.

In the object manager you can override each of the main request methods (which are supplied with success and failure blocks). You can implement these methods to call super but substituting the success and failure blocks with new versions which add some logic before calling the supplied versions.

Now, the additional logic would be a check of the response status. If it shows a token refresh is required it can be actioned and then the object manager can trigger a new load, using the parameters supplied in the first request.

Also, you shouldn't re-queue an operation unless the documentation states that it is supported as some operations won't work the second time they're executed...

Wain
  • 118,658
  • 15
  • 128
  • 151
  • Hi @Wain, nice to talk to you again, we had an AirPair session if you remember :) I'm having trouble repeating the request, specifically the success and failure blocks don't get triggered the second time although the call gets made. So you would suggest that I save those blocks as a property of the object manager and handle everything in there? – Sasha_K May 26 '14 at 08:49
  • I would create a new class to hold the parameters and store an instance of that (or a list of them if more requests come in while the re-auth is in progress). – Wain May 26 '14 at 11:42