Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 5505 invoked by uid 500); 22 Jul 2000 03:07:29 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 5494 invoked from network); 22 Jul 2000 03:07:29 -0000 Message-Id: X-Mailer: Novell GroupWise Internet Agent 5.5.3.1 Date: Fri, 21 Jul 2000 23:02:40 -0400 From: "Cliff Woolley" To: Subject: Re: buckets: null terminated strings? Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=_ECB4A1CA.BADBA474" X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. --=_ECB4A1CA.BADBA474 Content-Type: text/plain; charset=US-ASCII >>> rbb@covalent.net 07/21/00 10:47PM >>> >The big thing, is that these are NOT NULL-terminated strings. I got that much. =-) >The only thing they all have in common, is that they >all resolve to a string and a length. Although we allow people to get >just a pointer to the start of the string, it is always assumed that >people will get the start and the length. Some buckets won't require >this, but most will. This is the assumption that I was missing (ie, that people are forced to get the length from us). Hmm... could be asking for bugs, but it makes life easier for me. Okay, that's all I needed to know. I was actually going to suggest this as the way to go, but then I second-guessed myself. What can I say, it's late. So I'm giving up for the night anyway. I'll submit the insert-upon-creation patch I mentioned earlier sometime tomorrow. --Cliff Cliff Woolley Central Systems Software Administrator Washington and Lee University http://www.wlu.edu/~jwoolley/ Work: (540) 463-8089 Pager: (540) 462-2303 --=_ECB4A1CA.BADBA474 Content-Type: text/html; charset=ISO-8859-1

>>> rbb@covalent.net 07/21/00 10:47PM >>>

>The big thing, is that these are NOT NULL-terminated strings.

I got that much. =-)

>The only thing they all have in common, is that they
>all resolve to a string and a length. Although we allow people to get
>just a pointer to the start of the string, it is always assumed that
>people will get the start and the length. Some buckets won't require
>this, but most will.

This is the assumption that I was missing (ie, that people are forced to get the length from us). Hmm... could be asking for bugs, but it makes life easier for me. <grin> Okay, that's all I needed to know. I was actually going to suggest this as the way to go, but then I second-guessed myself. What can I say, it's late. <sigh> So I'm giving up for the night anyway. I'll submit the insert-upon-creation patch I mentioned earlier sometime tomorrow.

--Cliff

Cliff Woolley
Central Systems Software Administrator
Washington and Lee University
http://www.wlu.edu/~jwoolley/

Work: (540) 463-8089
Pager: (540) 462-2303

--=_ECB4A1CA.BADBA474--