From blu@sac.sfbay.sun.com Tue Dec 22 08:17:16 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id nBMGHGQa022621 for ; Tue, 22 Dec 2009 08:17:16 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id nBMGH6Bh026805; Tue, 22 Dec 2009 08:17:16 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KV200I1BAKSA700@nwk-avmta-1.sfbay.Sun.COM>; Tue, 22 Dec 2009 08:17:16 -0800 (PST) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KV200COCAKQQA20@nwk-avmta-1.sfbay.Sun.COM>; Tue, 22 Dec 2009 08:17:14 -0800 (PST) Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.226.132]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id nBMGHCFs006486; Tue, 22 Dec 2009 08:17:12 -0800 (PST) Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id nBMGHBEJ022616; Tue, 22 Dec 2009 08:17:11 -0800 (PST) Received: (from blu@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id nBMGHB9b022612; Tue, 22 Dec 2009 08:17:11 -0800 (PST) Date: Tue, 22 Dec 2009 08:17:11 -0800 (PST) From: Brian Utterback Subject: Add function pool_is_readonly_property to libpool [PSARC/2009/687 FastTrack timeout 01/05/2010] To: PSARC-ext@sun.com Cc: Mita.Solanky@sun.com Message-id: <200912221617.nBMGHB9b022612@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 3865 I am submitting this fasttrack on behalf of Mita Solanky. Binding is patch. Timeout is set to Jan. 5 to allow for the break. Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Add function pool_is_readonly_property to libpool 1.2. Name of Document Author/Supplier: Author: Mita Solanky 1.3 Date of This Document: 22 December, 2009 4. Technical Description libpool : addition of pool_is_readonly_property public interface A new f"unction pool_is_readonly_property" to be added to the existing pool property manipulation functions. This function provides a method to determine whether a pool property is readonly or not. The above is to be added to facilitate more economic retrieval of pool properties via poold and other consumers which currently suffer performance issues when retrieving large numbers of properties in the case where we have many components in a pool configuration (see CR 6836221), this change enables consumers to determine whether a property is readonly and therefore can be stored to subsequently be used without having to make further calls into libpool each time the property value is required. The libpool change will require an update to the man page man/3LIB/libpool as follows: INTERFACES The shared object libpool.so.1 provides the public inter- faces defined below. See intro(3) for additional information on shared object interfaces. pool_associate pool_component_info pool_component_to_elem pool_conf_alloc pool_conf_close pool_conf_commit pool_conf_export pool_conf_free pool_conf_info pool_conf_location pool_conf_open pool_conf_remove pool_conf_rollback pool_conf_status pool_conf_to_elem pool_conf_update pool_conf_validate pool_create pool_destroy pool_dissociate pool_dynamic_location pool_error pool_get_binding pool_get_owning_resource pool_get_pool pool_get_property pool_get_resource pool_get_resource_binding pool_get_status pool_info INTERFACES The shared object libpool.so.1 provides the public inter- faces defined below. See intro(3) for additional information on shared object interfaces. pool_associate pool_component_info pool_component_to_elem pool_conf_alloc pool_conf_close pool_conf_commit pool_conf_export pool_conf_free pool_conf_info pool_conf_location pool_conf_open pool_conf_remove pool_conf_rollback pool_conf_status pool_conf_to_elem pool_conf_update pool_conf_validate pool_create pool_destroy pool_dissociate pool_dynamic_location pool_error pool_get_binding pool_get_owning_resource pool_get_pool pool_get_property pool_get_resource pool_get_resource_binding pool_get_status pool_info pool_is_readonly_property pool_put_property The interface stability is uncommitted, matching the existing functions. The project binding is patch. 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From brian.utterback@sun.com Tue Dec 22 08:23:34 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id nBMGNY1s022760 for ; Tue, 22 Dec 2009 08:23:34 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.4) with ESMTP id nBMGNVmT010838 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Tue, 22 Dec 2009 09:23:33 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KV20021FAV94O00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 22 Dec 2009 08:23:33 -0800 (PST) Received: from dm-east-01.east.sun.com ([129.148.9.192]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KV200I03AV8OR70@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 22 Dec 2009 08:23:32 -0800 (PST) Received: from [129.148.9.171] (sr1-ubur-17.East.Sun.COM [129.148.9.171]) by dm-east-01.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id nBMGNUsh027150; Tue, 22 Dec 2009 11:23:30 -0500 (EST) Date: Tue, 22 Dec 2009 11:23:30 -0500 From: Brian Utterback Subject: Re: Add function pool_is_readonly_property to libpool [PSARC/2009/687 FastTrack timeout 01/05/2010] In-reply-to: <200912221617.nBMGHB9b022612@sac.sfbay.sun.com> To: Brian Utterback Cc: PSARC-ext@sun.com, Mita.Solanky@sun.com Message-id: <4B30F282.3000004@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 X-Enigmail-Version: 0.95.1 References: <200912221617.nBMGHB9b022612@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.24pre (X11/20091028) Status: RO Content-Length: 622 Brian Utterback wrote: > A new f"unction pool_is_readonly_property" to be added to the existing pool property manipulation functions. This function provides a method to determine whether a pool property is readonly or not. That should have been: A new function "pool_is_readonly_property" to be added... -- blu It's bad civic hygiene to build technologies that could someday be used to facilitate a police state. - Bruce Schneier ---------------------------------------------------------------------- Brian Utterback - Solaris RPE, Sun Microsystems, Inc. Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom From Sebastien.Roy@sun.com Wed Jan 6 09:41:54 2010 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o06Hfrxp010555 for ; Wed, 6 Jan 2010 09:41:54 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.4) with ESMTP id o06Hfrsb017986 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 6 Jan 2010 10:41:53 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KVU00G476HTC300@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Jan 2010 09:41:53 -0800 (PST) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KVU008WS6HS1D30@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Jan 2010 09:41:52 -0800 (PST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id o06Hfqn3024183 for ; Wed, 06 Jan 2010 17:41:52 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KVU00K006871E00@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Jan 2010 10:41:52 -0700 (MST) Received: from [192.168.1.5] ([unknown] [173.76.16.34]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KVU004VK6HQAE60@mail-amer.sun.com>; Wed, 06 Jan 2010 10:41:51 -0700 (MST) Date: Wed, 06 Jan 2010 12:41:49 -0500 From: Sebastien Roy Subject: Re: Add function pool_is_readonly_property to libpool [PSARC/2009/687 FastTrack timeout 01/05/2010] In-reply-to: <200912221617.nBMGHB9b022612@sac.sfbay.sun.com> Sender: Sebastien.Roy@sun.com To: Brian Utterback Cc: PSARC-ext@sun.com, Mita.Solanky@sun.com Message-id: <1262799709.1037.32.camel@seb> Organization: Sun Microsystems MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200912221617.nBMGHB9b022612@sac.sfbay.sun.com> Status: RO Content-Length: 1415 On Tue, 2009-12-22 at 08:17 -0800, Brian Utterback wrote: > libpool : addition of pool_is_readonly_property public interface > > A new function "pool_is_readonly_property" to be added to the existing pool > property manipulation functions. This function provides a method to determine > whether a pool property is readonly or not. > > The above is to be added to facilitate more economic retrieval of pool > properties via poold and other consumers which currently suffer performance > issues when retrieving large numbers of properties in the case where we have > many components in a pool configuration (see CR 6836221), this change enables > consumers to determine whether a property is readonly and therefore can be > stored to subsequently be used without having to make further calls into > libpool each time the property value is required. > > The libpool change will require an update to the man page man/3LIB/libpool Not architecture, but some man page needs to specify the function signature and semantics. It appears that libpool(3LIB) is not the only applicable man page. For example, pool_get_property(3POOL) contains a number of pool property related functions. The reason I bring it up is that the proposal doesn't specify what the function signature is, which would seem to be a crucial piece of information for a Public interface, and a proposed man page would have addressed that. -Seb From brian.utterback@sun.com Wed Jan 6 11:55:36 2010 Received: from sunmail6brm.central.sun.com (sunmail6brm.Central.Sun.COM [129.147.4.169]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o06JtQnO002643 for ; Wed, 6 Jan 2010 11:55:36 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail6brm.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o06JtPCh019178 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 6 Jan 2010 13:55:26 -0600 (CST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KVU00J01CO8SW00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Jan 2010 11:55:20 -0800 (PST) Received: from dm-east-01.east.sun.com ([129.148.9.192]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KVU00GROCO7U730@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Jan 2010 11:55:19 -0800 (PST) Received: from [129.148.9.171] (sr1-ubur-17.East.Sun.COM [129.148.9.171]) by dm-east-01.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o06Jst5l005097; Wed, 06 Jan 2010 14:54:56 -0500 (EST) Date: Wed, 06 Jan 2010 14:54:55 -0500 From: Brian Utterback Subject: Re: Add function pool_is_readonly_property to libpool [PSARC/2009/687 FastTrack timeout 01/05/2010] In-reply-to: <1262799709.1037.32.camel@seb> To: Sebastien Roy Cc: Brian Utterback , PSARC-ext@sun.com, Mita.Solanky@sun.com Message-id: <4B44EA8F.3010306@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 X-Enigmail-Version: 0.95.1 References: <200912221617.nBMGHB9b022612@sac.sfbay.sun.com> <1262799709.1037.32.camel@seb> User-Agent: Thunderbird 2.0.0.24pre (X11/20091028) Status: RO Content-Length: 2250 Sebastien Roy wrote: > On Tue, 2009-12-22 at 08:17 -0800, Brian Utterback wrote: >> libpool : addition of pool_is_readonly_property public interface >> >> A new function "pool_is_readonly_property" to be added to the existing pool >> property manipulation functions. This function provides a method to determine >> whether a pool property is readonly or not. >> >> The above is to be added to facilitate more economic retrieval of pool >> properties via poold and other consumers which currently suffer performance >> issues when retrieving large numbers of properties in the case where we have >> many components in a pool configuration (see CR 6836221), this change enables >> consumers to determine whether a property is readonly and therefore can be >> stored to subsequently be used without having to make further calls into >> libpool each time the property value is required. >> >> The libpool change will require an update to the man page man/3LIB/libpool > > Not architecture, but some man page needs to specify the function > signature and semantics. It appears that libpool(3LIB) is not the only > applicable man page. For example, pool_get_property(3POOL) contains a > number of pool property related functions. > > The reason I bring it up is that the proposal doesn't specify what the > function signature is, which would seem to be a crucial piece of > information for a Public interface, and a proposed man page would have > addressed that. > > -Seb > > Fair enough. Given that all 69 of the functions listed in libpool.so.3lib have their own man page in man3pool, I would say that it is reasonable to expect a new man page for this one as well. But now that I think about it, based on what the function does, wouldn't a better name be pool_property_is_readonly? The original form sounds like it is retrieving the property "pool_is_readonly" but this test is whether or not the property is readonly, isn't it? -- blu It's bad civic hygiene to build technologies that could someday be used to facilitate a police state. - Bruce Schneier ---------------------------------------------------------------------- Brian Utterback - Solaris RPE, Sun Microsystems, Inc. Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom From brian.utterback@sun.com Wed Jan 13 08:35:19 2010 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o0DGZInV015361 for ; Wed, 13 Jan 2010 08:35:18 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.4) with ESMTP id o0DGZBKZ023694 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 13 Jan 2010 09:35:18 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KW70071922TSO00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 13 Jan 2010 08:35:17 -0800 (PST) Received: from dm-east-01.east.sun.com ([129.148.9.192]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KW700K1422RJYE0@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 13 Jan 2010 08:35:15 -0800 (PST) Received: from [129.148.9.171] (sr1-ubur-17.East.Sun.COM [129.148.9.171]) by dm-east-01.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o0DGZBqB007357; Wed, 13 Jan 2010 11:35:12 -0500 (EST) Date: Wed, 13 Jan 2010 11:35:11 -0500 From: Brian Utterback Subject: Re: Add function pool_is_readonly_property to libpool [PSARC/2009/687 FastTrack timeout 01/05/2010] In-reply-to: <4B44EA8F.3010306@sun.com> To: Brian Utterback Cc: Sebastien Roy , Brian Utterback , PSARC-ext@sun.com, Mita.Solanky@sun.com Message-id: <4B4DF63F.1010309@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 X-Enigmail-Version: 0.95.1 References: <200912221617.nBMGHB9b022612@sac.sfbay.sun.com> <1262799709.1037.32.camel@seb> <4B44EA8F.3010306@sun.com> User-Agent: Thunderbird 2.0.0.24pre (X11/20091028) Status: RO Content-Length: 2583 The project team has agreed to add the man page and to use the name "pool_property_is_readonly". I believe that this takes care of all the open issues. The timer is past, and the extension requested at the last PSARC meeting has past. Can I get a +1 from somebody? Brian Utterback wrote: > > Sebastien Roy wrote: >> On Tue, 2009-12-22 at 08:17 -0800, Brian Utterback wrote: >>> libpool : addition of pool_is_readonly_property public interface >>> >>> A new function "pool_is_readonly_property" to be added to the existing pool >>> property manipulation functions. This function provides a method to determine >>> whether a pool property is readonly or not. >>> >>> The above is to be added to facilitate more economic retrieval of pool >>> properties via poold and other consumers which currently suffer performance >>> issues when retrieving large numbers of properties in the case where we have >>> many components in a pool configuration (see CR 6836221), this change enables >>> consumers to determine whether a property is readonly and therefore can be >>> stored to subsequently be used without having to make further calls into >>> libpool each time the property value is required. >>> >>> The libpool change will require an update to the man page man/3LIB/libpool >> Not architecture, but some man page needs to specify the function >> signature and semantics. It appears that libpool(3LIB) is not the only >> applicable man page. For example, pool_get_property(3POOL) contains a >> number of pool property related functions. >> >> The reason I bring it up is that the proposal doesn't specify what the >> function signature is, which would seem to be a crucial piece of >> information for a Public interface, and a proposed man page would have >> addressed that. >> >> -Seb >> >> > > Fair enough. Given that all 69 of the functions listed in > libpool.so.3lib have their own man page in man3pool, I would say that > it is reasonable to expect a new man page for this one as well. But > now that I think about it, based on what the function does, wouldn't a > better name be pool_property_is_readonly? The original form sounds > like it is retrieving the property "pool_is_readonly" but this test is > whether or not the property is readonly, isn't it? > -- blu It's bad civic hygiene to build technologies that could someday be used to facilitate a police state. - Bruce Schneier ---------------------------------------------------------------------- Brian Utterback - Solaris RPE, Sun Microsystems, Inc. Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom From Sebastien.Roy@sun.com Wed Jan 13 13:55:48 2010 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o0DLtmeT025820 for ; Wed, 13 Jan 2010 13:55:48 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o0DLtiRZ006576 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 13 Jan 2010 13:55:48 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KW700D1BGWZR600@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 13 Jan 2010 14:55:47 -0700 (MST) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KW700KTQGWZYD90@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 13 Jan 2010 14:55:47 -0700 (MST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id o0DLtkAw005064 for ; Wed, 13 Jan 2010 21:55:47 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KW700800G9H6900@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 13 Jan 2010 14:55:47 -0700 (MST) Received: from [192.168.1.5] ([unknown] [173.76.16.34]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KW700DGPGWSTSG0@mail-amer.sun.com>; Wed, 13 Jan 2010 14:55:41 -0700 (MST) Date: Wed, 13 Jan 2010 16:55:40 -0500 From: Sebastien Roy Subject: Re: Add function pool_is_readonly_property to libpool [PSARC/2009/687 FastTrack timeout 01/05/2010] In-reply-to: <4B4DF63F.1010309@sun.com> Sender: Sebastien.Roy@sun.com To: Brian Utterback Cc: Brian Utterback , PSARC-ext@sun.com, Mita.Solanky@sun.com Message-id: <1263419740.14312.25.camel@seb> Organization: Sun Microsystems MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200912221617.nBMGHB9b022612@sac.sfbay.sun.com> <1262799709.1037.32.camel@seb> <4B44EA8F.3010306@sun.com> <4B4DF63F.1010309@sun.com> Status: RO Content-Length: 341 On Wed, 2010-01-13 at 11:35 -0500, Brian Utterback wrote: > The project team has agreed to add the man page and to use the name > "pool_property_is_readonly". I believe that this takes care of all the > open issues. The timer is past, and the extension requested at the > last PSARC meeting has past. Can I get a +1 from somebody? +1 -Seb From Brian.Utterback@sun.com Wed Jan 13 14:10:10 2010 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o0DMA9vE026115 for ; Wed, 13 Jan 2010 14:10:09 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o0DMA8eO015328 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 13 Jan 2010 14:10:09 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KW700H2PHKXCB00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 13 Jan 2010 14:10:09 -0800 (PST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KW7007X6HKWXK40@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 13 Jan 2010 14:10:08 -0800 (PST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id o0DMA77a002017 for ; Wed, 13 Jan 2010 22:10:07 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KW700400H8CUI00@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 13 Jan 2010 15:10:07 -0700 (MST) Received: from [10.0.163.185] ([unknown] [192.18.41.196]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KW700FAQHKBPX90@mail-amer.sun.com>; Wed, 13 Jan 2010 15:09:47 -0700 (MST) Date: Wed, 13 Jan 2010 17:09:47 -0500 From: Brian Utterback Subject: Re: Add function pool_is_readonly_property to libpool [PSARC/2009/687 FastTrack timeout 01/05/2010] In-reply-to: <1263419740.14312.25.camel@seb> Sender: Brian.Utterback@sun.com To: Sebastien Roy Cc: Brian Utterback , PSARC-ext@sun.com, Mita.Solanky@sun.com Message-id: <4B4E44AB.1060308@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200912221617.nBMGHB9b022612@sac.sfbay.sun.com> <1262799709.1037.32.camel@seb> <4B44EA8F.3010306@sun.com> <4B4DF63F.1010309@sun.com> <1263419740.14312.25.camel@seb> User-Agent: Thunderbird 2.0.0.23 (X11/20091109) Status: RO Content-Length: 481 Thank you, Seb. As soon as I get to a terminal I'll set this case as closed approved. Sebastien Roy wrote: > On Wed, 2010-01-13 at 11:35 -0500, Brian Utterback wrote: > >> The project team has agreed to add the man page and to use the name >> "pool_property_is_readonly". I believe that this takes care of all the >> open issues. The timer is past, and the extension requested at the >> last PSARC meeting has past. Can I get a +1 from somebody? >> > > +1 > -Seb > >