July 11, 2009 at 13:27

What is expected in App Engine

    1. Service for working with large files.
    2. Inbox support
    3. XMPP API
    4. Support for mapping functions of datasets.
    5. Cursors for queries to the database - overcoming the limit of 1000 records.
    6. The system of warnings (alerts) about exceptional situations (exceptions) in custom applications.
    7. Dump and restore the storage system.
    Source: App Engine Product Roadmap

    1. Service for working with large files.
      When working with a DataStore, there is a limit on the size of an entity of 1 megabyte. One solution is to split the file into units and store them as separate entities. There is a separate library for such an operation - google-file-service , a description of which can also be found in  recipes (cookbook) on the App Engine website. The library is not part of the standard App Engine libraries.
      Apparently, Google is going to provide users with a similar library or introduce a new service that allows you to save large files without its explicit splitting into parts.
    2. Support for working with incoming mail
      App Engine has services that allow you to work with  external resources only through the HTTP and HTTPS protocol, as well as send e-mail messages on behalf of users with a Google account (Google account). What is meant by the inbox service I have the following option: there will be a library with functions for receiving messages from user mailboxes with Google accounts.
    3. XMPP API
      By analogy with sending e-mail , there will be a library for sending XMPP messages using a Google account.
    4. Support for the mapping function of datasets
      I have no idea what is meant here. Maybe the data mapping from Datastore, for example in XML , means  ? Or maybe some new types of connections between objects.
    5. Cursors for queries to the database - overcoming the limit of 1000 records.
      There is currently a limit on the number of records that can be returned when requested by Datastore. To work with a large number of records, you will have to make more than one request to the Datastore.
      In this case, Google programmers are likely to introduce a new class that will work as a cursor in other databases . When iterating over the cursor when going beyond 1000 records, a request for the following records will be implicitly made.
    6. Warning system A
      dump of all uncaught exceptions will be recorded and displayed in the administrative panel.
    7. Dump and restore the storage system.
      It will be possible to dump the current state of the database, save it on App Engine hosting and / or download to the local machine. The reverse dump recovery function will also be available.
    PS Thanks for the karma - moved the topic to the Google App Engine blog
    Tags:

    Also popular now: