From dev-return-17840-apmail-apr-dev-archive=apr.apache.org@apr.apache.org Sat Jan 06 15:23:45 2007 Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 68090 invoked from network); 6 Jan 2007 15:23:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Jan 2007 15:23:43 -0000 Received: (qmail 94805 invoked by uid 500); 6 Jan 2007 15:23:49 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 94760 invoked by uid 500); 6 Jan 2007 15:23:49 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 94749 invoked by uid 99); 6 Jan 2007 15:23:49 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Jan 2007 07:23:49 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of lucian.grijincu@gmail.com designates 66.249.92.171 as permitted sender) Received: from [66.249.92.171] (HELO ug-out-1314.google.com) (66.249.92.171) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Jan 2007 07:23:39 -0800 Received: by ug-out-1314.google.com with SMTP id 44so5916916uga for ; Sat, 06 Jan 2007 07:23:18 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=qcBsfXGmOGYKMtxBZGh82S+Md/NUyA0H6zrrN2im7DbdR/AlWkDFoK3VE48rB62j7NUUclYCT93wjbI7fSvD+a24Z7HdDnaePVKuoPOm5PEaZdTJv1ck91D08oU9F4JKBjIh8rJ/UnlygsgrHijE7f3sjIKtWrrqkYClSgiVZtw= Received: by 10.78.193.19 with SMTP id q19mr3510307huf.1168096998443; Sat, 06 Jan 2007 07:23:18 -0800 (PST) Received: by 10.78.16.5 with HTTP; Sat, 6 Jan 2007 07:23:18 -0800 (PST) Message-ID: Date: Sat, 6 Jan 2007 17:23:18 +0200 From: "Lucian Adrian Grijincu" To: dev@apr.apache.org Subject: New Vista APIs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org Vista come with a set of new APIs http://msdn2.microsoft.com/en-us/library/aa904937.aspx "Slim reader/writer (SRW) locks enable the threads of a single process to access shared resources; they are optimized for speed and occupy very little memory." the interface is very similar to the one APR has in http://apr.apache.org/docs/apr/trunk/group__apr__thread__rwlock.html implementing apr_thread_rwlock through these APIs would be very simple: we almost only have to call the corresponding OS functions. the same stands for Condition variables: http://msdn2.microsoft.com/en-us/library/ms682052.aspx "Condition variables are synchronization primitives that enable threads to wait until a particular condition occurs. Condition variables are user-mode objects that cannot be shared across processes." I haven't looked any further into the matter (performance of the new APIs relative to APR's current implementation, or if there are any other new Vista APIs that may simplify the APR's implementation of x and y functions), but I wanted to get your opinion on this: is there any desire to have (with a compile time switch) APR's functions implemented through the new set op API's ? -- Best Regards, Lucian Adrian Grijincu