🚀 go-pugleaf

"CC" <XXmailsink@aol.com> wrote in message
news:3f3d7670@newsgroups.borland.com...

> Does it sound resonable that one of these standard C
> library calls could not be playing nicely with multiple
> tthreads running at the same time?

Only if multiple threads were accessing the same file/socket without
synchronizing between them so that only 1 thread were accessing them at any
given time.

> int TMyThread::myFileOpen(.......)
> {
>     int fd;
>
>     EnterCriticalSection(&cs)
>     fd = open(.....);
>     LeaveCriticalSection(&cs)
>    return fd;
>
> }

What exactly are you planning on doing with 'fd'?  All you've done is
protect the initial opening the file.  Unless you are calling
EnterCriticalSection() again, you are not going to be protecting the
modifying of the file as well.  If you want to protect the file during the
entire transfer, you should be calling EnterCriticalSection() when you open
the file and LeaveCriticalSection() after you have closed it.  Otherwise you
should rethink your design.

> Also the same for read/writing sockets, writing files,etc.

TServerSocket already performs locking operations internally to protect
itself.


Gambit