Hi PK, You shouldn't do any sort of special checks. Instead, use the API. In the case of remote_api, don't specify the appid at all. Instead, specify the endpoint (e.g. a.appspot.com/_ah/remote_api or localhost: 8080/_ah/remote_api). The tool will look up the app id.
--Matthew On Jul 13, 1:51 pm, PK <[email protected]> wrote: > Matthew, > > thanks for the reply. > > In our tests we use remote API extensively. The same datastore is updated > from either the server or remote API code. The remote API scripts need to be > given the appid and we have an environment variable defining it. Of course > this is now broken. I am retreating to a mechanism that says "if you are > operating agains the dev datastore then the APPID is "dev~" + real_app_id > else it is real_app_id", I am hopeful this will fix the issues. > > Between working around this issue and the further "regression" of 3643 (see > my comment there) I have not yet been able to pass our automated tests with > 1.5.2_prerelease > > Anyway, I am optimistic, and look forward to starting simplifying some of my > indexes next. I have been waiting for more than a year for that :-) > > Thanks, > PK -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
