On Sun, 10 Oct 2004 09:12:53 +0200, Dror Shilo <[EMAIL PROTECTED]> wrote:
> > Incidentally, will "apr_os_thread_current( )" work on all platforms
> > (specifically, Linux and Win32)? Am I understanding this correctly to mean
> > that the function works on all platforms, but the return value is
> >
number for the current process
Dror
-Original Message-
From: David Barrett [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 28, 2004 11:12 PM
To: Dror Shilo
Cc: dev@apr.apache.org
Subject: RE: Threads Best Practices
> -Original Message-
> From: Dror Shilo [mailto:[EM
> -Original Message-
> From: Dror Shilo [mailto:[EMAIL PROTECTED]
> Subject: RE: Threads Best Practices
>
> 1) you can put null
> 2) see apr samples
>
> void * APR_THREAD_FUNC ThreadProc(apr_thread_t *, void *context)
> {
> }
> 3)use
> apr
Message-
From: David Barrett [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 28, 2004 7:36 AM
To: dev@apr.apache.org
Subject: Threads Best Practices
Hi there, I'm really starting to get into APR. I was able to port to APR
mutexes without a hitch. However, I'm a bit confused on th
Hi there, I'm really starting to get into APR. I was able to port to APR
mutexes without a hitch. However, I'm a bit confused on threads, and I'd
appreciate any direction you can offer:
1) What should I do with "apr_threadattr_t"? Need I create one, or can I
pass NULL for that field into "apr_
