Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

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

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-05 15:32 -0400
Organization A noiseless patient Spider
Message-ID <oc3giq$p0r$1@dont-email.me> (permalink)
References <58e3cbbe$0$739$e4fe514c@news.xs4all.nl> <oc0l9v$jd0$1@dont-email.me> <58e406b4$0$733$e4fe514c@news.xs4all.nl> <oc11cm$2kq$1@dont-email.me> <58e4a21b$0$745$e4fe514c@news.xs4all.nl>

Show all headers | View raw

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

| > I chose to get around that by having a Busy property in
| > my AxEXE. So I don't need anything like Sleep.
|
| And that tight loop still allows events to be handled ?
|
Yes. Because it's tight.

While Obj.Busy = True
Wend

  That leaves it checking constantly. When my component
makes a file request via winsock it makes it through a
winsock userControl. If that request is OK it sets Busy = True.
The winsock UC then sends an event when the file is
finished downloaded. With that event the component
raises the event for the scriot, OnDownloadFinish, and
then sets Busy = False.

  It gets complicated, but doing things in that order
seems to work.

Back to microsoft.public.scripting.vbscript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

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