Groups > microsoft.public.scripting.vbscript > #11614

Re: MSWinsock.ocx - server: handle more than a single connection & share events

From	"Mayayana" <mayayana@invalid.nospam>
Newsgroups	microsoft.public.scripting.vbscript
Subject	Re: MSWinsock.ocx - server: handle more than a single connection & share events
Date	2017-04-06 09:42 -0400
Organization	A noiseless patient Spider
Message-ID	<oc5gff$mpi$1@dont-email.me> (permalink)
References	(2 earlier) <58e406b4$0$733$e4fe514c@news.xs4all.nl> <oc11cm$2kq$1@dont-email.me> <58e4a21b$0$745$e4fe514c@news.xs4all.nl> <oc3giq$p0r$1@dont-email.me> <58e5f913$0$707$e4fe514c@news.xs4all.nl>

Show all headers | View raw

"R.Wieser" <address@not.available> wrote

| One drawback though:  that method will most likely keep your processor
| running at 100% ...
|

  Interesting point. That seems true, but it doesn't
seem to work that way. All compiled software is
basically running a loop to keep going. And there's
no freezeup.

  I don't know how it works technically.

  I'd guess that maybe the process just forfeits its
CPU timeslice each time it comes around, so that
no CPU load is recorded. That would explain how
20 processes can be loaded but not using resources.
They're all prepared to respond in the next microsecond
that they're offered a timeslice, but they pass on the
offer. Like a bottle of wine being passed endlessly
around at an AA meeting. The wine is never dissipated
but is always available in short order if anyone decides
to drink.

Thread

MSWinsock.ocx - server: handle more than a single connection & share events "R.Wieser" <address@not.available> - 2017-04-04 18:37 +0200
  Re: MSWinsock.ocx - server: handle more than a single connection & share events "Mayayana" <mayayana@invalid.nospam> - 2017-04-04 13:34 -0400
    Re: MSWinsock.ocx - server: handle more than a single connection & share events "R.Wieser" <address@not.available> - 2017-04-04 22:49 +0200
      Re: MSWinsock.ocx - server: handle more than a single connection & share events "Mayayana" <mayayana@invalid.nospam> - 2017-04-04 17:00 -0400
        Re: MSWinsock.ocx - server: handle more than a single connection & share events "R.Wieser" <address@not.available> - 2017-04-05 09:52 +0200
          Re: MSWinsock.ocx - server: handle more than a single connection & share events "Mayayana" <mayayana@invalid.nospam> - 2017-04-05 15:32 -0400
            Re: MSWinsock.ocx - server: handle more than a single connection & share events "R.Wieser" <address@not.available> - 2017-04-06 10:15 +0200
              Re: MSWinsock.ocx - server: handle more than a single connection & share events "Mayayana" <mayayana@invalid.nospam> - 2017-04-06 09:42 -0400
                Re: MSWinsock.ocx - server: handle more than a single connection & share events "R.Wieser" <address@not.available> - 2017-04-06 17:47 +0200
  Re: MSWinsock.ocx - server: handle more than a single connection & share events JJ <jj4public@vfemail.net> - 2017-04-05 00:42 +0700
    Re: MSWinsock.ocx - server: handle more than a single connection & share events "R.Wieser" <address@not.available> - 2017-04-04 23:03 +0200
  RE: MSWinsock.ocx - server: handle more than a single connection & share events Mr. E < meme@me.com> - 2017-04-14 04:55 +0000
    Re: MSWinsock.ocx - server: handle more than a single connection & share events "R.Wieser" <address@not.available> - 2017-04-14 09:12 +0200

csiph-web