-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Move the 'thread-local stack' implementation up from datastore. #622
Move the 'thread-local stack' implementation up from datastore. #622
Conversation
Preparing to tackle #15, which needs similar support in storage.
# limitations under the License. | ||
"""Thread-local resource stack. | ||
|
||
Not an API. |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
LGTM (I think you should clarify the module docstring, but do as you see fit). |
@tseaver When merged can you ping me and point at the next PR in line? |
I'm still working on the next-in-line (it is the real meat of #15). |
See: #622 (comment). [ci skip].
Move the 'thread-local stack' implementation up from datastore.
OK cool |
Just took a peek. I feel like the multipart stuff will have been handled already by @craigcitro Also, what sorts of API requests are allowed with batch? Any and all? |
I didn't see any of that in Batching can handle |
writing from my phone - but apitools has full batch support. see base/py/batch.py |
I didn't see the batching support in @craigcitro It looks like the |
|
@tseaver ah, i probably don't export |
Preparing to tackle #15, which needs similar support in storage.