Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 5468 invoked by uid 6000); 4 Sep 1999 01:09:20 -0000 Received: (qmail 5460 invoked from network); 4 Sep 1999 01:09:18 -0000 Received: from gremlin.ics.uci.edu (mmdf@128.195.1.70) by taz.hyperreal.org with SMTP; 4 Sep 1999 01:09:18 -0000 Received: from kiwi.ics.uci.edu ( fielding@kiwi.ics.uci.edu [128.195.21.109] ) by gremlin-relay.ics.uci.edu id aa29712 for ; 3 Sep 1999 18:09 PDT To: new-httpd@apache.org Subject: Re: Maintaining status tables across restart In-reply-to: Your message of "Fri, 03 Sep 1999 14:09:09 EDT." <01JFJBEMHWYA8ZDY93@er6s1.eng.ohio-state.edu> Date: Fri, 03 Sep 1999 18:09:14 -0700 From: "Roy T. Fielding" Message-ID: <199909031809.aa29712@gremlin-relay.ics.uci.edu> Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org >For maximum portability, you don't want to have shared data structures >containing address pointers - all processes don't necessarily map the memory >to the same virtual address. You store whatever it is that the shared memory library is using as an access handle (a.k.a., a shared memory pointer). The only thing that will ever use it is the status module, whether that be for snmp or web queries, and it will have to use the shared memory library to map the handle to a read-only memory address. ....Roy