Re: Problems with SO_REUSEADDR

Tech-Archive recommends: Fix windows errors by optimizing your registry

Arkady,

thanks for the reply!

Matthias Moetje
-------------------------------------
TERASENS GmbH
Augustenstraße 24
80333 Munich, GERMANY
-------------------------------------
Fon: +49 89 143370-0
Fax: +49 89 143370-22
e-mail: moetje at terasens dot com
www: www.terasens.com
-------------------------------------

"Arkady Frenkel" <arkadyf@xxxxxxxxxxxxxxxx> wrote in message
news:%23YxftPNTGHA.5440@xxxxxxxxxxxxxxxxxxxxxxx
Masshias!
Additionally , you succeed in setting
SO_REUSEADDR because/if you did it on different threads ( that fail if you
do it on the same thread,

because of design Terry wrote in details ) and I agree with Eugene that
you
don't need to use 2 sockets for read and write but the same one

Arkady

"Matthias Moetje [MVP]" <moetje@xxxxxxxxxxxxxxxxxxx> wrote in message
news:e%23xezlITGHA.5172@xxxxxxxxxxxxxxxxxxxxxxx
Eugene,

thanks very much for your reply?

Why would you do that? Sockets are full-duplex, you can both send and
receive on a signle one.

I know that. OK, here's the story: I am developing a TAPI service
provider
(TSP).
This is actually a dll that is loaded by the telephony service.

The TSP comes with an MSP (Media Service Provider). The MSP is COM based
and lives in the process of the client application. The TSP communicates
with the MSP
through TAPI messages. These are dispatched by the telephony service to
the
the TAPI client (TAPI3.dll) which loads the MSP into the client
application's process.
This design is by MS and there is nothing I can change about that.

Part of the MSP are two COM classes, a capture stream and a render
stream.
I can send messages from my TSP to the capture and the render stream COM
object. These two objects don't know anything about each other and
cannot
communicate. So the question is: Where should I create the socket?
I can't create it in the TSP because it lives in a different process and
I
can't create
it in only one of the stream objects because it can't be passed to the
other
one.

Thus, I ended up creating two sockets (which works fine unless the
source
port must be identical to the receiving port)


SO_REUSEADDR is intended to be used in totally different scenario.

Which one? I found only little information about it..



Best regards,

Matthias Moetje
-------------------------------------
TERASENS GmbH
Augustenstraße 24
80333 Munich, GERMANY
-------------------------------------
Fon: +49 89 143370-0
Fax: +49 89 143370-22
e-mail: moetje at terasens dot com
www: www.terasens.com
-------------------------------------






.

Relevant Pages

  • Re: A problem about MSP & File Terminal
    ... Is the graph set up in the MSP correctly ... Matthias Moetje ... TERASENS GmbH ...
    (microsoft.public.win32.programmer.tapi)
  • Re: What does it mean when get a LINEERR_REINIT on lineOpen?
    ... to stop and restart the telephony service but usually that fails to stop ... Matthias Moetje ... TERASENS GmbH ...
    (microsoft.public.win32.programmer.tapi)
  • Re: CISCO IPCC Call Center
    ... they only supported TAPI v2.x which was fine by me. ... if their TSP would have its own MSP. ... Matthias Moetje ... TERASENS GmbH ...
    (microsoft.public.win32.programmer.tapi)
  • Re: ITAddressCapabilities and Bitwise and
    ... The MSP ... who is responsible for transfering stream to terminal ... >> Matthias Moetje ... >> TERASENS GmbH ...
    (microsoft.public.win32.programmer.tapi)
  • Re: CME_STREAM_FAIL
    ... The RCA MSP is for NDIS devices. ... This interface and method are documented in the DirectX SDK ... Matthias Moetje ... TERASENS GmbH ...
    (microsoft.public.win32.programmer.tapi)