TID: Mystic BBS 1.12 A47   
   MSGID: 1:129/215 f92eca2d   
   REPLY: 2:250/6 2b65a983   
   TZUTC: -0400   
    LW> 1) Does Mystic pass a blocking or non-blocking socket handle?   
      
   Blocking   
      
    LW> 2) With regard to point 1, is there an established standard which all BBS   
    LW> systems adhere to (i.e. blocking or non-blocking)?   
      
   The only standard that I know of that ever attempted to define anything was   
   Mystic's DOOR32 and that uses blocking sockets.  I assume you'd probably get   
   blocking from most BBSes then by default, but I can't say for sure what other   
   software does.   
      
    LW> 3) If the door changes socket mode, should this be undone prior to exit?   
      
   I think it'd be a good practice to do this.   
      
   The original intention was that the socket should be duplicated before being   
   passed to the door, but I think in practice that didn't end up being   
   guarenteed or even done at all because of variations in operating systems (and   
   if I am not mistaken some OSes specifically said that sockets should not be   
   duplicated).   
      
   I didn't have the foresight back in the 1990s to specifically call this stuff   
   out in the DOOR32 docs unfortunately and now I forget most of the details like   
   this.  It was all pretty new back then and I was inexperienced.   
      
    LW> 4) Is the door expected to perform winsock clean-up if the client   
    LW> performs an impromptu disconnect?   
      
   It *might* be safe to call only when it drops but I can't say for sure without   
   experimentation.   
      
   If I remember correctly calling WSACleanup is a Windows specific thing and it   
   invalidates any socket handles used by the process. For that reason I think it   
   was not called in any case within D32 doors.  Instead it let the BBS detect   
   the connection loss and do what it does.   
      
   Things may behave differently depending of if/when the socket was duplicated   
   by the BBS before being passed, but I would   
   operate on the assumption that the socket is not duplicated.   
      
   --- Mystic BBS v1.12 A47 2021/06/07 (Windows/32)   
    * Origin: Sector 7 | Mystic WHQ (1:129/215)   
   SEEN-BY: 1/123 90/1 103/705 105/81 120/340 457 616 123/10 131 124/5016   
   SEEN-BY: 129/215 305 154/10 30 40 50 700 203/0 220/80 90 221/0 6 226/18   
   SEEN-BY: 226/30 227/114 201 702 229/101 310 424 426 452 550 700 981   
   SEEN-BY: 229/1016 1017 240/1120 5411 5824 5832 5853 6309 249/206 307   
   SEEN-BY: 249/317 400 280/464 5003 282/1038 292/854 8125 301/1 317/3   
   SEEN-BY: 320/219 322/757 342/200 396/45 633/280 770/1 2452/250 2454/119   
   SEEN-BY: 3634/12   
   PATH: 129/215 154/10 280/464 240/5832 229/426