Date: Thu, 14 Oct 1999 09:47:18 -0400 (EDT)
From: Ryan Bloom <rbb@raleigh.ibm.com>
To: new-httpd@apache.org
Subject: Re: multithreaded & static char[]
In-Reply-To: <060201bf15d0$d49e7ac0$4600a8c0@bluprints.com>
Message-ID: 
 <Pine.LNX.4.04.9910140945130.24142-100000@chosondo.raleigh.ibm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org


We are using a static string, because we are emulating a UNIX standard
function, which uses a static string.  We do not need any locking, because
of how this is used.  If you look at where this function is used, it is
ONLY used in support programs, which are by definition single threaded.

In the future, we may want to change this to be thread-safe, but it is not
an immediate concern for Apache.

Ryan

On Thu, 14 Oct 1999, Henrik Vendelbo wrote:

> While I looked for the _getch, I noticed "static char password[MAX_STRING_LEN];". 
> 
> Is there some kind of semaphore check to avoid two treads using getpass at the same time ?
> 
> \Henrik
> 

_______________________________________________________________________
Ryan Bloom		rbb@raleigh.ibm.com
4205 S Miami Blvd	
RTP, NC 27709		It's a beautiful sight to see good dancers 
			doing simple steps.  It's a painful sight to
			see beginners doing complicated patterns.