Hi, For further clarification on the Gmail namespace issue - It *used* to be the case that you could not register your own Gmail name as an app id. We have changed this so that you can reserve a Gmail name as an app id only when signed in with that Gmail name.
However, once you have reserved an app id, it will no longer be available in App Engine or as a Gmail name. As such, in order to have both an app id and a Gmail name be the same, you need to first register the Gmail name, then register the app id. -Marzia On Wed, Feb 18, 2009 at 9:58 AM, [email protected] < [email protected]> wrote: > > One way to do this if you don't need real-time responsiveness would be > to have the application check a mail feed. I haven't played around > with any Python IMAP libraries, but I assume that there would be a way > to do this. > > Once they add scheduling--which is on the roadmap--there's no reason > you couldn't have it check an email account every few minutes to see > if any new emails have come up and execute the appropriate actions. > > If you need realtime responsiveness, then clearly having a mechanism > for AppSpot to receive an email and fire off your application as > appropriate would be awesome. There was someone out there who wrote > an app for doing something like that and open-sourced it; if you have > your own server elsewhere, you could configure it to receive those > emails and fire off a request to your app. Unfortunately, I don't > know the name of it, but if you search the archives of this group, I'm > sure you'll find it. > > -Ben > > On Feb 18, 3:04 am, Peter <[email protected]> wrote: > > > allows apps to recieve mail (presumably at > > > <appname>@gmail.com). > > > > Allowing apps to receive and perform specific actions based on email > > content is something I'd really like to see implemented. > > > > I think it would make more sense to avoid the gmail.com namespace. A > > couple of alternatives I can think of: > > > > 1) Support email receipt on personally registered domain names that > > are using Google Apps > > 2) Automatically create a matching mailox under the appspot.com TLD > > name (<appname>@appspot.com) > > 3) Allow creation of a varying number of mailboxes under > > <mailbox>@<appname>.appspot.com > > > > On Feb 15, 9:33 am, Ian Lewis <[email protected]> wrote: > > > > > I'm guessing the gmail shared namespace limitation has to do with being > able > > > to the forthcoming release that allows apps to recieve mail (presumably > at > > > <appname>@gmail.com). This is probably something they thought about in > the > > > beginning but just didn't implement. > > > > > On Sun, Feb 15, 2009 at 7:56 AM, Alexander Konovalenko < > [email protected]>wrote: > > > > > > There's an issue to remove the Gmail shared namespace limitation: > > > >http://code.google.com/p/googleappengine/issues/detail?id=479 > > > > > > Also, Marzia says that they don't allow similar names. For example, > if > > > > 'appid' is already registered, you won't be able to create an app > > > > called 'app1d'. > > > > > -- > > > ======================================= > > > 株式会社ビープラウド イアン・ルイス > > > 〒150-0012 > > > 東京都渋谷区広尾1-11-2アイオス広尾ビル604 > > > email: [email protected] > > > TEL：03-5795-2707 > > > FAX：03-5795-2708http://www.beproud.jp/ > > > ======================================= > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
