From: "Aaron Bannert" <[EMAIL PROTECTED]> Sent: Monday, July 23, 2001 5:44 PM
> Quick implementation question. I've got this working as described above > under UNIX, but I'd like to do this correctly and I've run into a small > issue. > > I'm not seeing a reason for having apr_thread_info_t in the first place, > and I think we should just override apr_thread_t with the data we need. > It's already private, and OS2 is already doing it this way. Are there > any reasons I wouldn't just do it the same way? We would end up with > something like this: Hmmm... since it is private, I don't suppose there is a potential problem. I'm fine, either way. Anyone seeing anything around the corner we've missed with using the same apr_thread_t to both the creator and created threads?
