Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 18777 invoked by uid 500); 27 Sep 2002 16:00:35 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 18753 invoked from network); 27 Sep 2002 16:00:34 -0000 Date: Fri, 27 Sep 2002 09:00:55 -0700 From: Justin Erenkrantz To: dev@httpd.apache.org Subject: Re: Saving request state when client uses byte ranges Message-ID: <20020927160055.GM17893@scotch.ics.uci.edu> Mail-Followup-To: Justin Erenkrantz , dev@httpd.apache.org References: <200209270911.g8R9Blde024631@scotch.ics.uci.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200209270911.g8R9Blde024631@scotch.ics.uci.edu> User-Agent: Mutt/1.4i X-Spam-Status: No, hits=-13.4 required=5.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01, USER_AGENT,USER_AGENT_MUTT version=2.50-cvs X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Fri, Sep 27, 2002 at 02:11:47AM -0700, dev-return-33593-apmail-jerenkrantz=apache.org@httpd.apache.org wrote: > Can anyone suggest a way around this problem? Is my shared memory idea > workable? Is there another way that I'm just blindly missing? Well, one thing I'd guess you could do is only charge when they receive the final byterange? (Yes, a client could request it out-of-order or do everything but the last byte, but...) You could use shmem, but that'll fail whenever the server is restarted. And, I'd guess byteranges would be most prevalent (in normal use) when the server is restarted. =) -- justin