-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support authorization in datastore #6
Conversation
Also take into account the owner when creating the urls.
return True | ||
return False | ||
global public_key |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to use global
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wanted to have a singleton pattern here, so that we load the public_key only once and lazily (i.e. only on first request). How would you do it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd just load it with the module. But global
is fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK - the reason I didn't go that way was to avoid a network request upon importing the module.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
@akariv I'm done. Some comments to address before merge. Most are trivial points, but I think you should at least create an issue for the refactor of the class pattern. |
18d4d28
to
46e37a0
Compare
@pwalsh - I fixed some of the issues and created #7 |
@akariv great. looks good. ok to merge. |
Support authorization in datastore
We change the way the datastore authenticates requests.
It used to be with API keys, now it's with a cryptographic token.
Some other changes here: