Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 10713 invoked from network); 4 Sep 2006 23:37:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 Sep 2006 23:37:12 -0000 Received: (qmail 86217 invoked by uid 500); 4 Sep 2006 23:37:11 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 86186 invoked by uid 500); 4 Sep 2006 23:37:11 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 86177 invoked by uid 99); 4 Sep 2006 23:37:11 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Sep 2006 16:37:11 -0700 X-ASF-Spam-Status: No, hits=2.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,RCVD_IN_BL_SPAMCOP_NET,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of peeter.piegaze@gmail.com designates 66.249.82.231 as permitted sender) Received: from [66.249.82.231] (HELO wx-out-0506.google.com) (66.249.82.231) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Sep 2006 16:37:09 -0700 Received: by wx-out-0506.google.com with SMTP id t13so2158492wxc for ; Mon, 04 Sep 2006 16:36:49 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=hxtwCReuD6mnY+Aafd+nPM9jPuQP087NbrbANlMqs8Jzx+wufNRY+pGuFSSMN1I/fboL3jdzRcfm+XavuUMR0Y5KG1zH+j5xyjVc08vBBWLJQwQphXrEDMuDWnmzIZ76/kWSaDrqDHaPxh22bcDHz4m8WI04iWfDmtj/SPFDV64= Received: by 10.90.56.14 with SMTP id e14mr1184032aga; Mon, 04 Sep 2006 16:36:49 -0700 (PDT) Received: by 10.90.73.17 with HTTP; Mon, 4 Sep 2006 16:36:48 -0700 (PDT) Message-ID: <3df33a250609041636i4481ca6ahf5b151f063f2fcc5@mail.gmail.com> Date: Mon, 4 Sep 2006 19:36:48 -0400 From: "Peeter Piegaze" Sender: peeter.piegaze@gmail.com To: dev@jackrabbit.apache.org Subject: Re: SORRY Re: JSR 283: hard links are NOT back In-Reply-To: <44FCAF69.10406@adelphia.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <44FCAB8F.4080302@adelphia.net> <44FCAF69.10406@adelphia.net> X-Google-Sender-Auth: 65e56d8fb45813d9 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi Dan, In JSR 283 we plan to support a feature very similar to hard links. The Early Draft of 283 has been submited to the JCP and should be publically available very soon, so you will be able to see for yourself. Cheers, Peeter On 9/4/06, Dan Connelly wrote: > My mistake. I was looking at an old JSR 170 spec. But my question > remain the same. Hard links would be really nice to have. Either > that or very strong soft link support. > > > > Dan Connelly wrote: > > > I see from the archives that hard links were removed from Jackrabbit > > when they got removed from the JSR 170 spec. > > > > The "Multiple Parent" requirement (Section 6.11), a/k/a hard links, is > > back in the early draft of JSR 283. Did hard links ever work in > > Jackrabbit? Could JR turn on its support for hard links in some > > future release, or is this feature just a spec writer's pipe dream? > > > > Am I right in assuming that this feature was considered too *nix-ish > > for an MS-ish world? > > > > Is the real world satisfied having only REFERENCE-based soft links to > > mix:referenceables? > > > > -- Dan > > > >