Return-Path: X-Original-To: apmail-jackrabbit-oak-dev-archive@minotaur.apache.org Delivered-To: apmail-jackrabbit-oak-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 45CD99E2B for ; Thu, 15 Mar 2012 13:07:33 +0000 (UTC) Received: (qmail 37380 invoked by uid 500); 15 Mar 2012 13:07:33 -0000 Delivered-To: apmail-jackrabbit-oak-dev-archive@jackrabbit.apache.org Received: (qmail 37359 invoked by uid 500); 15 Mar 2012 13:07:33 -0000 Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: oak-dev@jackrabbit.apache.org Delivered-To: mailing list oak-dev@jackrabbit.apache.org Received: (qmail 37349 invoked by uid 99); 15 Mar 2012 13:07:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Mar 2012 13:07:32 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of julian.reschke@gmx.de designates 213.165.64.22 as permitted sender) Received: from [213.165.64.22] (HELO mailout-de.gmx.net) (213.165.64.22) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 15 Mar 2012 13:07:25 +0000 Received: (qmail invoked by alias); 15 Mar 2012 13:07:04 -0000 Received: from unknown (EHLO [42.1.3.190]) [192.147.117.12] by mail.gmx.net (mp012) with SMTP; 15 Mar 2012 14:07:04 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX19Knj1Kt1lKrhlp9d7m9u4CKgYEHU9TdL+kZCkhBL XQIpr0EVWnZRQ0 Message-ID: <4F61E977.7080209@gmx.de> Date: Thu, 15 Mar 2012 14:07:03 +0100 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: oak-dev@jackrabbit.apache.org Subject: SNS and dumping nodes into the repo Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Virus-Checked: Checked by ClamAV on apache.org Hi there, as far as I understand, one of the use cases that comes up for allowing same name siblings is that it makes easier for a client just to import "random stuff" into a collection without having to worry about naming. JSR-333 specifies a variant of addNode where the final node name is picked by the client, while a name hint can still be made. This is somewhat similar to the createTempFile API in Java, or POSTing collection members in AtomPub (Slug: header field, ), or even POSTing to WebDAV collections (). Maybe, if oak allowed this pattern, we can avoid having to implement the stronger SNS semantics? Best regards, Julian