Re: How to cancel select() call ?

I have to release any mutex before I enter select() and during that time,
after releasing mutex and before entering select(), socket can be closed by
my application because of an event, and immediately after that another
socket, with the same descriptor, can be created by other thread / there are
a few, completely independent threads, which create sockets in my
application /, and that / random / socket will be added to select().

Kamil

U¿ytkownik "Arkady Frenkel" <arkadyf@xxxxxxxxxxxxxxxx> napisa³ w wiadomo¶ci
news:OZbAb65mHHA.568@xxxxxxxxxxxxxxxxxxxxxxx
Why ? "after select() exits and before I create disposable socket again
there is a time when socket descriptor will be invalid." - is place for
mutex and OTOH use the same mutex to enter the code which create socket
Arkady

"kamil" <kamildobk@xxxxxxxxxxxxxxxxx> wrote in message
news:%234$xQP4mHHA.4624@xxxxxxxxxxxxxxxxxxxxxxx
But there is no good place to put that mutex - in this case I won't close
any socket by accident but, instead of this, I can add a random socket to
select() set.

Kamil


U¿ytkownik "Arkady Frenkel" <arkadyf@xxxxxxxxxxxxxxxx> napisa³ w
wiadomo¶ci news:ezSHSXqmHHA.568@xxxxxxxxxxxxxxxxxxxxxxx
Use sync object ( mutex ) in this case to allow main thread to
reallocate
socket before other thread will try to do the same
Arkady

"kamil" <kamildobk@xxxxxxxxxxxxxxxxx> wrote in message
news:en7llYkmHHA.5024@xxxxxxxxxxxxxxxxxxxxxxx
I found some cross-platform network library for RTP/RTCP protocol. It
works well, but I have one problem - it uses select() in its main loop.
I need a way to cancel select() call from another thread as fast as
possible when some events in my application are invoked ( to make a new
connection ). I know that I can add 'disposable socket' to a socket set
and close it when I want select to be cancelled, but I'm not sure if it
is completely safe method. Lets say my event loop looks like this:

create_disposable_socket()
while()
{
select()
if ( myevent ) <--------------------- insafe, socket descriptor
invalid ?????
{
create_disposable_socket_again();
handle_my_app_events()
}
else
{
handle_network_events();
}
}

But after select() exits and before I create disposable socket again
there is a time when socket descriptor will be invalid. What if some
other thread create socket which reuse the same descriptor - it can be
closed because my application thread still thinks that it is a
disposable socket created to cancel select !
Is it possible or am I missing something ?

Thanks you in advance,
Kamil









.

Relevant Pages

  • Re: How to cancel select() call ?
    ... "after selectexits and before I create disposable socket again ... there is a time when socket descriptor will be invalid." ... I know that I can add 'disposable socket' to a socket set ...
    (microsoft.public.win32.programmer.networks)
  • Re: How to cancel select() call ?
    ... Microsoft MVP, MCSD ... after releasing mutex and before entering select, socket can be closed ... there is a time when socket descriptor will be invalid." ... But after selectexits and before I create disposable socket again ...
    (microsoft.public.win32.programmer.networks)
  • Re: translating "create Semaphore" to Linux
    ... GHUM wrote: ... print "application allready running" ... why use a Semaphore rather than a Mutex? ... Windows won't allow you to rebind the same socket to the ...
    (comp.lang.python)
  • Re: How to cancel select() call ?
    ... know that I can add 'disposable socket' to a socket set and close it when I ... is a time when socket descriptor will be invalid. ... created to cancel select! ...
    (microsoft.public.win32.programmer.networks)
  • Re: How to cancel select() call ?
    ... after releasing mutex and before entering select, socket can be closed by ... Your socket descriptor is never released, ...
    (microsoft.public.win32.programmer.networks)