RE: UDP Sockets

Answers are inlined

  _____  

From: Mahmoud Hammoud [mailto:[email protected]] 
Sent: Tuesday, September 30, 2008 6:55 AM
To: [email protected]
Cc: Jyotsana Rathore; Gregory Wright; [email protected]
Subject: UDP Sockets

 

Dear All,

I would really appreciate reasonably detailed answers to the following 2
questions (urgent), this would represent a gread push to my project. I am
developing under windows and interested in RTP transport over UDP of mp4
media.

1) Where exactly (class::function) are the socket API functions sendto(...)
and recvfrom(...) called at the server and client respectively? I am just
interested in the actual transmission through the socket API (i.e. at the
lowest level) and I am quite frustrated with all the OS abstractions
available within the source code.

In the client code, the API functions sendto(..) and recvfrom(..) are in
\common\netio\pub\platform\win\hxwinsocklib.h and
\common\netio\pub\platform\win\hxwinsocklib.cpp which is a WinSock API
wrapper. It dynamically loads/unloads Winsock dll.

2) Suppose I comment the function calls in 1), to replace them by similar
ones but on a socket (only one) I create myself, still passing the received
"buffers" appropriately to the upper layers, would this work? I know that
each stream in the presentation (audio and video) has its own UDP socket,
but does this mean that the socket IO functions are called in a threaded
manner and that the data received on the audio stream's socket will be
stored in a transport buffer for that stream (and same for video)? That is,
are the different streams buffered separately at the transport layer (based
on the stream number maybe)?

            Yes, a transport buffer object is created for each stream
received by the Helix Client. Each transport buffer object has a separate
queue for data.


Thank you in advance,

Mahmoud Hammoud

_______________________________________________
Helix-client-dev mailing list
[email protected]
http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev