Feature request

[GAEfan]

I have a request which I think will help clean up the migration mess to HRD.  I can understand why we would need to create a new HRD app (with new app name) and then migrate the old MS app to it.

But then, why can't we delete the old app, wait the 72 hours, then reactivate that old app name as an HRD app?  Then, we could migrate the HRD app back to it, thus preserving our original app name.

In other words, say we have a current MS app:  greatappname.appspot.com.  Currently, we have to lose that greatappname, and migrate to some greatappname-with-hyphen.appspot.com, thus losing greatappname forever.  According to the docs: " Once your application is actually deleted, however, you cannot recover its state or data. Only its application ID remains (and this can never be re-used)."

This is a bit sloppy.  Why cannot we reclaim the old greatappname, activate it as an HRD app, and clean up our app names?

Thank you for considering my request.

[Drake]

I don’t understand why people get tied to “Great name”  to me a great name is a hash, generated just before I deploy, guaranteed unique. Impossible to remember, unlikely to be randomly discovered.  And when you hit the app by that ID you get a 410 error.

 

Only the URL with your own .com would be known to the world.

 

We don’t do this internally because the dashboard shows the AppID not the App Name, and so the humans get sad, when they can’t tell which app is theirs.

[GAEfan]

It runs a bit deeper than that, for some of us use the appspot address for SSL:  https://greatappname.appspot.com

[Barry Hunter]

>
> In other words, say we have a current MS app: greatappname.appspot.com.
> Currently, we have to lose that greatappname, and migrate to some
> greatappname-with-hyphen.appspot.com, thus losing greatappname forever.

No. You can keep greatappname forever, it just becomes an alias to
greatappname-with-hyphen

Nobody need know about the actual App ID change. To the outside, the
app still works on the old name.

>
> Thank you for considering my request.

Requests should actully go on the issue tracker :)
http://code.google.com/p/googleappengine/

[Jeff Schnitzer]

This doesn't seem like a good idea either. It can't inspire
confidence to see *.appspot.com in the URL bar. And you should never,
_ever_ deploy mobile clients hardcoded to a domain that you don't
fully control.

A further problem with appspot.com is the fact that anyone can visit
xyzversion.yourapp.appspot.com. Old versions potentially read/write
data in obsolete formats. We keep our version strings non-guessable.

Jeff

On Wed, Sep 5, 2012 at 11:01 AM, GAEfan <ken...@gmail.com> wrote:
> It runs a bit deeper than that, for some of us use the appspot address for
> SSL: https://greatappname.appspot.com
>

> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/d15-cxDB0L4J.
>
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengi...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.