Return-Path: Delivered-To: apmail-incubator-shindig-dev-archive@locus.apache.org Received: (qmail 81563 invoked from network); 1 Dec 2008 22:17:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Dec 2008 22:17:25 -0000 Received: (qmail 91884 invoked by uid 500); 1 Dec 2008 22:17:36 -0000 Delivered-To: apmail-incubator-shindig-dev-archive@incubator.apache.org Received: (qmail 91475 invoked by uid 500); 1 Dec 2008 22:17:35 -0000 Mailing-List: contact shindig-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: shindig-dev@incubator.apache.org Delivered-To: mailing list shindig-dev@incubator.apache.org Received: (qmail 91464 invoked by uid 99); 1 Dec 2008 22:17:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Dec 2008 14:17:35 -0800 X-ASF-Spam-Status: No, hits=-1.8 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of weitzelm@us.ibm.com designates 32.97.110.151 as permitted sender) Received: from [32.97.110.151] (HELO e33.co.us.ibm.com) (32.97.110.151) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Dec 2008 22:16:06 +0000 Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e33.co.us.ibm.com (8.13.1/8.13.1) with ESMTP id mB1MA0XT032150 for ; Mon, 1 Dec 2008 15:10:00 -0700 Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id mB1MAZlO222500 for ; Mon, 1 Dec 2008 15:10:35 -0700 Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id mB1MAYx0007993 for ; Mon, 1 Dec 2008 15:10:34 -0700 Received: from d03mc133.boulder.ibm.com (d03mc133.boulder.ibm.com [9.17.195.209]) by d03av01.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id mB1MAYEK007983 for ; Mon, 1 Dec 2008 15:10:34 -0700 In-Reply-To: References: To: shindig-dev@incubator.apache.org MIME-Version: 1.0 Subject: appData query... X-KeepSent: 6B219FDE:C41B9588-85257512:0076D692; type=4; name=$KeepSent X-Mailer: Lotus Notes Build V85_M2_08202008 August 20, 2008 From: Mark D Weitzel Message-ID: Date: Mon, 1 Dec 2008 17:10:33 -0500 X-MIMETrack: Serialize by Router on D03MC133/03/M/IBM(Release 8.0.1|February 07, 2008) at 12/01/2008 15:10:33, Serialize complete at 12/01/2008 15:10:33 Content-Type: multipart/alternative; boundary="=_alternative 0079B8C185257512_=" X-Virus-Checked: Checked by ClamAV on apache.org --=_alternative 0079B8C185257512_= Content-Type: text/plain; charset="US-ASCII" Maybe someone can answer a quick question regarding an appData query using vanilla shindig. When I request the following: http://.../social/rest/appdata/canonical/@self What is returned is: {"entry":{"canonical":{"size":"100","count":"2"}}} This seems to make sense since there is no {appId} parameter specified, and in the canonicaldb.json, the "size" and "count" fields don't appear to be associated with any specific appId. However, I was looking for the text in the spec (e.g. section 6.4 of the restful API) that indicated this was a valid query. If the {appId} parameter is left off, then you return all {appId} values? If I then make the request: http://.../social/rest/appdata/canonical/@self/1 What is returned is: {"entry":{"canonical":{"size":"100","count":"2"}}} I'm probably reading canonicaldb.json incorrectly, but I don't see where the same two fields, "size" and "count" are associated with an {addId} of "1". I expected an empty result for this query. Can someone help clarify this for me? Thanks, -Mark W. _______________________________________________________________________________________________________________ Mark Weitzel | STSM | IBM Software Group | (919) 543 0625 | weitzelm@us.ibm.com --=_alternative 0079B8C185257512_=--