Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. sendto(); question.

sendto(); question.

Scheduled Pinned Locked Moved C / C++ / MFC
questionhelpjsonannouncement
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • E Offline
    E Offline
    esepich
    wrote on last edited by
    #1

    Feel free to correct me at any time as I am still trying my best to learn this API. I know that there is a SOCKADDR structure that is able to hold data and family type. I also know that there is a SOCKADDR_IN structure that is able to hold an address, a port number, data and a family type. I have a sendechorequest function set up like this int CSSPingDlg::SendEchoRequest(SOCKET s, SOCKADDR_IN lpstToAddr); Now comes the interesting part. Inside this SendEchoRequest function I make a call to the sendto() function. What I take issue with is the fifth parameter of sendto(); which requires a SOCKADDR * that is supposed to contain the address of the host to which to send the data. The problem is that my ping program requires that I use a SOCKADDR_IN structure which is able to hold important information like the IP address of the host. Is there a version of sendto(); that will allow me to pass a SOCKADDR_IN instead of a plain SOCKADDR? Could it be that I am just not using sendto(); correctly. All I know is that I want to send data to the host specified in the SOCKADDR_IN structure that I have passed to my sendechorequest function. How do I do that?

    S 1 Reply Last reply
    0
    • E esepich

      Feel free to correct me at any time as I am still trying my best to learn this API. I know that there is a SOCKADDR structure that is able to hold data and family type. I also know that there is a SOCKADDR_IN structure that is able to hold an address, a port number, data and a family type. I have a sendechorequest function set up like this int CSSPingDlg::SendEchoRequest(SOCKET s, SOCKADDR_IN lpstToAddr); Now comes the interesting part. Inside this SendEchoRequest function I make a call to the sendto() function. What I take issue with is the fifth parameter of sendto(); which requires a SOCKADDR * that is supposed to contain the address of the host to which to send the data. The problem is that my ping program requires that I use a SOCKADDR_IN structure which is able to hold important information like the IP address of the host. Is there a version of sendto(); that will allow me to pass a SOCKADDR_IN instead of a plain SOCKADDR? Could it be that I am just not using sendto(); correctly. All I know is that I want to send data to the host specified in the SOCKADDR_IN structure that I have passed to my sendechorequest function. How do I do that?

      S Offline
      S Offline
      Steve Mayfield
      wrote on last edited by
      #2

      From MSDN doc of sendto() The Microsoft TCP/IP Sockets Developer’s Kit only supports the Internet address domains. To actually fill in values for each part of an address, you use the SOCKADDR_IN data structure, which is specifically for this address format. The SOCKADDR and the SOCKADDR_IN data structures are the same size. You simply cast to switch between the two structure types. Steve

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups