Return-Path: X-Original-To: apmail-db-jdo-dev-archive@www.apache.org Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4FDCB612C for ; Wed, 13 Jul 2011 22:36:34 +0000 (UTC) Received: (qmail 96734 invoked by uid 500); 13 Jul 2011 22:36:33 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Received: (qmail 96720 invoked by uid 99); 13 Jul 2011 22:36:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jul 2011 22:36:33 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [74.125.82.172] (HELO mail-wy0-f172.google.com) (74.125.82.172) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jul 2011 22:36:27 +0000 Received: by wyj26 with SMTP id 26so485673wyj.31 for ; Wed, 13 Jul 2011 15:36:06 -0700 (PDT) Received: by 10.216.60.17 with SMTP id t17mr1470078wec.29.1310596566092; Wed, 13 Jul 2011 15:36:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.90.143 with HTTP; Wed, 13 Jul 2011 15:35:46 -0700 (PDT) In-Reply-To: References: From: Matthew Adams Date: Wed, 13 Jul 2011 17:35:46 -0500 Message-ID: Subject: Re: Asynchronous database ops in JDO - something for the future? To: jdo-dev@db.apache.org, db@dawnbreaks.net Content-Type: multipart/alternative; boundary=000e0cd66d4ac40a7c04a7fb0a37 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd66d4ac40a7c04a7fb0a37 Content-Type: text/plain; charset=ISO-8859-1 Hi David, Interesting ideas. If you can, please file a JIRA so that we can track it. It would probably be related to issue https://issues.apache.org/jira/browse/JDO-651 . -matthew On Mon, Jul 11, 2011 at 7:14 PM, David Bullock wrote: > Hi JDO specification folk, > > One environment where I'd like to use JDO is Google AppEngine's datastore, > and that datastore specifies a way of working with data where one fires off > the query and then gets the results from a Future some time later [1]. (I > am sure Andy knows all about it lately :-)). > > As far as I know, JDO doesn't currently standardise a way of working with > datastores in an async manner. Maybe that would be an interesting problem > for JDO 4 some day? As datastores increasingly become non-local and > latencies for operations become high, getting a callback when the datastore > is finished is a convenient way of working with it. > > cheers, > David. > > [1] > > http://code.google.com/appengine/docs/java/javadoc/com/google/appengine/api/datastore/AsyncDatastoreService.html > -- @matthewadams12 mailto:matthew@matthewadams.me skype:matthewadams12 yahoo:matthewadams aol:matthewadams12 google-talk:matthewadams12@gmail.com msn:matthew@matthewadams.me http://matthewadams.me http://www.linkedin.com/in/matthewadams --000e0cd66d4ac40a7c04a7fb0a37--