• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 22 subscribers
  • Views 1423 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

tcp_get_socket and tcp_release_socket

F D

Hi,

I need some deeper explanation of tcp_get_socket and tcp_release_socket. I noticed that a socket allocated with tcp_get_socket and returned with tcp_release_socket cannot be allocated with tcp_get_socket again.

Is my assumption correct or do I something wrong?
Do I have to build my own socket manager in case I have to allocate and de-allocate sockets?

I appreciate your feedback!

Thank you,
Frank

Parents
  • 0 in reply to Catcus Blip

    Hi Tamir,

    I have to adapt to an TCP communication approach using dynamically created connections (3rd party - I cannot post). The interface requires to get a Socket and to return a Socket if the connection is closed. I noticed that with the Keil TCP/IP stack I can only allocate the number of Sockets I specified in Net_Config.c.
    I cannot access return sockets using tcp_get_socket.

    Thank you,
    Frank

Reply
  • 0 in reply to Catcus Blip

    Hi Tamir,

    I have to adapt to an TCP communication approach using dynamically created connections (3rd party - I cannot post). The interface requires to get a Socket and to return a Socket if the connection is closed. I noticed that with the Keil TCP/IP stack I can only allocate the number of Sockets I specified in Net_Config.c.
    I cannot access return sockets using tcp_get_socket.

    Thank you,
    Frank

Children
No data