Hi Neil, The App Engine Search <https://cloud.google.com/appengine/docs/java/search/> API service is accessible via the "API" of the libraries provided to the App Engine runtime in the given language. External access to the Search service for an app should be done through sending requests to handlers on your app (even an Endpoints API <https://cloud.google.com/appengine/docs/java/endpoints/>) which can access the Search API. Therefore, writing a "client library" for a custom runtime would involve writing a "wrapper" or "middle-ware" application in Java, Python, or Go which could access the Search API.
I hope this helps you move forward with your development, and specifically in reference to custom runtimes, I'm sure development will proceed with making these services accessible via a REST API (don't quote me, though), rather than simply being embedded in the runtime for the main supported languages of traditional GAE. If you'd like, there is a public issue tracker for App Engine <https://code.google.com/p/googleappengine/issues/list>, and I encourage you to create a feature request asking for a REST API for Search API (and any other App Engine services which don't expose a REST API). Sincerely, Nick On Friday, May 29, 2015 at 9:18:09 AM UTC-4, Neil Rao wrote: > > That's cool. Is there a client library for the App Engine Search service? > I can't find any, so I thought I'd write one, but I couldn't find any > publicly accessible interfaces for it (REST etc). -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/78981b64-77da-4e0f-8aa5-caa45d0f9201%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
