tag:blogger.com,1999:blog-33400508.post7347752829871873040..comments2012-01-04T03:22:39.512-08:00James Urquharthttp://www.blogger.com/profile/07869296024524739031noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-33400508.post-74829078578918980302009-11-22T22:40:43.285-08:002009-11-22T22:40:43.285-08:00[url=http://firgonbares.net/][img]http://firgonbares.net/img-add/euro2.jpg[/img][/url]<br />[b]buy cheap software oem, [url=http://firgonbares.net/]buy open source software[/url]<br />[url=http://firgonbares.net/][/url] WinZip 12 Pro harvard software purchase<br />software in canada [url=http://firgonbares.net/]g1 software store[/url] buying softwares<br />[url=http://firgonbares.net/]lp software store[/url] how do i download acdsee 9<br />[url=http://firgonbares.net/]icon windows xp midi[/url] acdsee 6<br />sell free software [url=http://firgonbares.net/]cheap softwares[/b]Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-33400508.post-39234349696437402082008-04-15T13:04:00.000-07:002008-04-15T13:04:00.000-07:00James,<BR/><BR/>Good post, I agree with almost everything you've said. That said, it would be fairly trivial to create a data exporter as Chris states. I think Tim is wrong on this particular point.<BR/><BR/>However the "critical mass via network effects" type of lock-in which Tim points to is very real, this is particularly a problem with proprietary clouds.<BR/><BR/>As for the ceilings, this was an approach we followed with Zimki to begin with. Why? Because the pricing models and security methods are particularly sensitive to activity and the ceilings gave us a chance to manage this.<BR/><BR/>As for game changing - it happened as soon as they let the open SDK out and people started talking about and building equivalent environments.<BR/><BR/>On that note, well done Chris.swardleyhttp://www.blogger.com/profile/04702421918430488600noreply@blogger.comtag:blogger.com,1999:blog-33400508.post-90553926102204712912008-04-15T13:00:00.000-07:002008-04-15T13:00:00.000-07:00From the appengine blog http://googleappengine.blogspot.com/2008/04/were-up-and-running.html<BR/><BR/>..some of the general areas we're focusing on right now.. <BR/><BR/>"Support for offline processing. Right now Google App Engine is great for web apps that do all of their processing in response to user requests, but what about apps that need to perform scheduled tasks or larger-scale data migration? We'd like to support those apps too."<BR/><BR/>..and ..<BR/><BR/>"Support for large files. Google App Engine currently imposes a limit of 1MB on all requests, both inbound and outbound. We're interested in providing efficient support for much larger uploads and downloads"<BR/><BR/>TomTom Gleesonhttp://blog.gobansaor.comnoreply@blogger.comtag:blogger.com,1999:blog-33400508.post-12941864309580705422008-04-15T12:06:00.000-07:002008-04-15T12:06:00.000-07:00James,<BR/><BR/>I don't see why Google needs to offer anything special for data export. It would be a relatively simple task to write a data exporter that converted all an application's data to JSON and returned it to the http requester. You'd have to do some pagination to keep the requests under the time-limit, but there'd really be nothing to it.jChrishttp://www.blogger.com/profile/11598260533932670972noreply@blogger.com