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
{{ message }}
This repository has been archived by the owner on Nov 30, 2023. It is now read-only.
More of a question than a bug - for webapp2 version 2.3, in webapp_extras there was a protorpc.py file which implemented protorpc remote / service_mapping for webapp2.
My existing application uses webapp2, protorpc has code for webapp and wsgi. I guess what I'm trying to accomplish is registering my protorpc remote.methods with my existing webapp2 application. Is there an easy way to accomplish this with the current version?
My existing application already has a webapp2.RequestHandler and webapp2.WSGIApplication and is running under AppEngine standard environment.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
More of a question than a bug - for webapp2 version 2.3, in webapp_extras there was a protorpc.py file which implemented protorpc remote / service_mapping for webapp2.
My existing application uses webapp2, protorpc has code for webapp and wsgi. I guess what I'm trying to accomplish is registering my protorpc remote.methods with my existing webapp2 application. Is there an easy way to accomplish this with the current version?
My existing application already has a webapp2.RequestHandler and webapp2.WSGIApplication and is running under AppEngine standard environment.
The text was updated successfully, but these errors were encountered: