9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: boyd.roberts@ca-indosuez.com
To: 9fans@cse.psu.edu
Subject: Réf. : Re: [9fans] mothra
Date: Tue, 18 Jul 2000 15:35:55 +0200	[thread overview]
Message-ID: <41256920.005072A4.00@SNPAR12.> (raw)



given i wrote a DLL (to my shame) once that talked SOCKS4
transparently and sat on top of winsock (ie. it looked like
winsock) i saw what socket calls netscape made.  i was less than
impressed.  i just had a look at the winsock code in mozilla.
yep, as i expected -- clueless bozos.

check this:

   BOOL IsWinsockLoaded (int sp)
   {
        if (hWinsock == NULL)
        {
            WSADATA wsaData;
            WSAStartup(0x0101, &wsaData);
        }
    //  Quick macro to tell if the winsock has actually loaded for a particular
    //      function.
    //  Debug version is a little more strict to make sure you get the names
   right.
    #ifdef DEBUG
        return hWinsock != NULL && spArray[(int)(sp)] != NULL;
    #else //  A little faster
        return hWinsock != NULL;
    #endif
    }

this _abortion_ is called before _every_ winsock call.

duh... load it on startup and chuck away a swath of
redundant, inefficient code;  bugs waiting to happen.

and THIS:

            WSAStartup(0x0101, &wsaData);

a hard wired _constant_?

the prosecution rests.

i even saw a telnet that looped on write() after making an async
connect().  duh, select() anyone?




             reply	other threads:[~2000-07-18 13:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-18 13:35 boyd.roberts [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-07-19 16:08 boyd.roberts
2000-07-19 12:05 boyd.roberts
2000-07-19 10:12 boyd.roberts
2000-07-19 10:10 boyd.roberts
2000-07-18 13:18 boyd.roberts
2000-07-18  9:52 boyd.roberts

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41256920.005072A4.00@SNPAR12. \
    --to=boyd.roberts@ca-indosuez.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).