Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 50937 invoked from network); 22 Feb 2007 20:24:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Feb 2007 20:24:40 -0000 Received: (qmail 5913 invoked by uid 500); 22 Feb 2007 20:24:48 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 5698 invoked by uid 500); 22 Feb 2007 20:24:47 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 5688 invoked by uid 99); 22 Feb 2007 20:24:47 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Feb 2007 12:24:47 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [68.142.198.204] (HELO smtp105.sbc.mail.mud.yahoo.com) (68.142.198.204) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 22 Feb 2007 12:24:35 -0800 Received: (qmail 82094 invoked from network); 22 Feb 2007 20:24:13 -0000 Received: from unknown (HELO ?127.0.0.1?) (ddebrunner@sbcglobal.net@75.24.109.206 with login) by smtp105.sbc.mail.mud.yahoo.com with SMTP; 22 Feb 2007 20:24:12 -0000 X-YMail-OSG: jUh1VJAVM1mA8w9.noLkJuvJ5ifS7xVediS7C_CxeLXUZwUFkR5UAt9EHnmQT9opmwHK5AP_Xw1CADHtexkMkuizd4G7H.nvwGLEriIzfh_jcd0DdKiNkUv4T7hW9VSb5qz4HZQsyYupVr8- Message-ID: <45DDFBD2.2090809@apache.org> Date: Thu, 22 Feb 2007 12:23:46 -0800 From: Daniel John Debrunner User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: Q: Should Derby 10.3 be Derby 11? References: <20070220122438.GB4110@atum01.norway.sun.com> <45DB6E9A.2050107@sun.com> <45DBE340.1020503@apache.org> <45DDC3F4.80509@sun.com> <45DDD1DD.20702@apache.org> <45DDD57E.8010505@sun.com> <45DDD8F3.6080602@apache.org> <45DDDEE1.3050901@sun.com> <45DDE4CF.3050704@apache.org> <45DDF76A.9020604@sun.com> In-Reply-To: <45DDF76A.9020604@sun.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Rick Hillegas wrote: > Daniel John Debrunner wrote: >> Rick Hillegas wrote: >> >>> Thanks, Dan. I have updated the wiki page to clarify that the >>> restrictions depend on authentication. >> >> Thanks, two more questions: >> >> In the first table there is the phrase "Among other side-effects" >> What are these side effects, as it is it doesn't really help anyone >> make a judgment call as to if they will be effected or not? >> >> In the first table there are the phrases "instrument her code" and >> "instrument the rest of her application". I don't know what >> "instrument" means here, could you expand on what such a user would >> need to do? >> >> I update the sections a little to be clear on if authentication was >> system or database, feel free to modify if what's I've changed is wrong. >> >> Thanks, >> Dan. >> > Thanks for the additional feedback. I have tried to clarify the > incompatibility entries for the secure server. Thanks, I modified the page to make it reflect reality. Simply adding privilege blocks will not work when running with policy file installed by the network server. Also removed the "may affect", since there's no "may" about it, operations in routines that need security checks will fail with the security policy installed by the network server. Dan.