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
Copy file name to clipboardExpand all lines: README.rdoc
+10-14Lines changed: 10 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ life cycle methods that operate against a persistent store.
53
53
As you can see, the methods are quite similar to Active Record's methods for dealing with database
54
54
records. But rather than dealing directly with a database record, you're dealing with HTTP resources (which may or may not be database records).
55
55
56
-
Connection settings (`site`, `headers`, `user`, `password`, `proxy`) and the connections themselves are store in
56
+
Connection settings (`site`, `headers`, `user`, `password`, `bearer_token`, `proxy`) and the connections themselves are store in
57
57
thread-local variables to make them thread-safe, so you can also set these dynamically, even in a multi-threaded environment, for instance:
58
58
59
59
ActiveResource::Base.site = api_site_for(request)
@@ -69,28 +69,24 @@ Active Resource supports the token based authentication provided by Rails throug
69
69
You can also set any specific HTTP header using the same way. As mentioned above, headers are thread-safe, so you can set headers dynamically, even in a multi-threaded environment:
0 commit comments