It's easy to do that, I agree... indeed that's what I am doing. But it seems NONSENSE (see Wooble reply above ;) and an unnecessary hassle if we only knew an approx date for paid accounts (and binaryproperty size limits, etc).
On Sep 18, 9:21 am, cb <[EMAIL PROTECTED]> wrote: > It's pretty easy to send your uploads/downloads to amazon s3 while > you're waiting for google to catch up. That way you can use appengine > to build the framework and amazon can hold the data until appengine is > ready to go with unlimited/pay per use storage. > > On Sep 17, 9:44 am, FreeAgent <[EMAIL PROTECTED]> wrote: > > > Hello to the GAE team! > > > I've been a fan of App Engine since launch. > > > Last night, I attended a talk on Amazon Web Services and I got into a > > discussion with potential clients about using AWS to serve their > > needs. > > > Afterwards, I thought of a design using App Engine. > > > The hitch is: it's a high-bandwidth application which could surpass > > the 10,000 MB limits (on upload and download) from App Engine. The CPU- > > cycle limits could be exceeded too, but they're harder to estimate. > > > On the other hand, it will take some time to implement the > > application, so we may be able to wait until more resources are > > available from App Engine. > > > Can you offer firm dates for the availability of more bandwidth & > > cycles--and billing for those resources? (I know you said it would be > > before year-end.) > > > Thanks and regards, > > > Kevin Noonan, > > Dublin, Ireland. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---