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. Mobile Development
  3. Mobile
  4. Why would Microsoft not support all options to setsockopt?

Why would Microsoft not support all options to setsockopt?

Scheduled Pinned Locked Moved Mobile
hardwarehelpquestion
2 Posts 2 Posters 2 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.
  • C Offline
    C Offline
    charlieg
    wrote on last edited by
    #1

    I'm going to go surf the support boards, but maybe someone here has an idea. If you go look at the documentation for setsockopt under Windows CE 5.0, you will read this: The following list shows BSD options that are not supported for setsockopt . SO_ACCEPTCONN SO_RCVLOWAT SO_RCVTIMEO SO_SNDLOWAT SO_SNDTIMEO SO_TYPE Today I did some poking around as our next project will be on Windows Compact Embedded 7. I'm reading for Windows Compact 2013, the same options are not supported. If anything, Microsoft is consistent. :omg: <-- for the humor impaired. Anyone out there know as to why Microsoft would not / never support the full BSD socket implementation? I can work around it (it's coyote ugly), but I'm just curious.

    Charlie Gilley Stuck in a dysfunctional matrix from which I must escape... “Let me give you a tip on a clue to men's characters: the man who damns money has obtained it dishonorably; the man who respects it has earned it.”

    H 1 Reply Last reply
    0
    • C charlieg

      I'm going to go surf the support boards, but maybe someone here has an idea. If you go look at the documentation for setsockopt under Windows CE 5.0, you will read this: The following list shows BSD options that are not supported for setsockopt . SO_ACCEPTCONN SO_RCVLOWAT SO_RCVTIMEO SO_SNDLOWAT SO_SNDTIMEO SO_TYPE Today I did some poking around as our next project will be on Windows Compact Embedded 7. I'm reading for Windows Compact 2013, the same options are not supported. If anything, Microsoft is consistent. :omg: <-- for the humor impaired. Anyone out there know as to why Microsoft would not / never support the full BSD socket implementation? I can work around it (it's coyote ugly), but I'm just curious.

      Charlie Gilley Stuck in a dysfunctional matrix from which I must escape... “Let me give you a tip on a clue to men's characters: the man who damns money has obtained it dishonorably; the man who respects it has earned it.”

      H Offline
      H Offline
      Herman T Instance
      wrote on last edited by
      #2

      Why did the chicken cross the road-question? Better ask Microsoft.

      In Word you can only store 2 bytes. That is why I use Writer.

      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