Return-Path: Delivered-To: apmail-incubator-abdera-user-archive@locus.apache.org Received: (qmail 18830 invoked from network); 10 Sep 2007 20:48:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Sep 2007 20:48:35 -0000 Received: (qmail 35178 invoked by uid 500); 10 Sep 2007 20:48:28 -0000 Delivered-To: apmail-incubator-abdera-user-archive@incubator.apache.org Received: (qmail 35159 invoked by uid 500); 10 Sep 2007 20:48:28 -0000 Mailing-List: contact abdera-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: abdera-user@incubator.apache.org Delivered-To: mailing list abdera-user@incubator.apache.org Received: (qmail 35142 invoked by uid 99); 10 Sep 2007 20:48:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Sep 2007 13:48:28 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jasnell@gmail.com designates 209.85.132.249 as permitted sender) Received: from [209.85.132.249] (HELO an-out-0708.google.com) (209.85.132.249) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Sep 2007 20:48:24 +0000 Received: by an-out-0708.google.com with SMTP id b33so159309ana for ; Mon, 10 Sep 2007 13:48:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; bh=qfVKSs5QpfSmJjGBpc6EBX2jOXUpAoH/GNX86HkPMIA=; b=NJJXV17/mu7z+rll4I8j/PDIwf/iX2dvlm36aUrCrkcuBF8PmYkR/9gNEU7OqK6pC/HShpmQNehiqM4kophmbRW5LOkRoBZVpyc/C2ubU2wQaIXLKVL6YNUbude9kf6NYa7+eSfKMFz5LHRIaWoq+4KR1EUwKUS09zpjd0Z/DF8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=JbIm5q2iTwuPCW9+JB5HCBbgLJr1b4r8ErMbk0oRwnQT6ph6M39qjCM7UWPR58j1BMdKOAl2seJEnzf6WpoyfWl3f3ZePOuvUIT5jSqxwcGBrMxGgaVz4mqoJ29Miw0zgYerNS2zajQE+FBOPDOSJ/+tdfRyPM7+pod6yQjMCvs= Received: by 10.100.34.16 with SMTP id h16mr5223032anh.1189457283609; Mon, 10 Sep 2007 13:48:03 -0700 (PDT) Received: from ?192.168.1.2? ( [67.181.218.96]) by mx.google.com with ESMTPS id g7sm4494481wra.2007.09.10.13.48.02 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 10 Sep 2007 13:48:03 -0700 (PDT) Message-ID: <46E5AD80.9060901@gmail.com> Date: Mon, 10 Sep 2007 13:48:00 -0700 From: James M Snell User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: abdera-user@incubator.apache.org Subject: Re: mediaPost/entryPost? References: <46E5AACB.5020600@mulesource.com> In-Reply-To: <46E5AACB.5020600@mulesource.com> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org The Atompub spec does not define POST to entry and media resources but it does not disallow them either. Those methods are there primarily to make it easy to support those operations should a provider so desire... even tho doing so means going beyond the base protocol. - James Dan Diephouse wrote: > Hiya, I'm a bit confused about a part of the Provider API. The > mediaPost/entryPost APIs seem to imply that people are doing a POST to > an Atom entry. I'm probably missing something super obvious here, but > under what situations does that occur? I thought posts were strictly to > collections. > > - Dan >