N
Nico
Hello everyone,
I have re-formulated the question I asked on my last post::
I am trying to capture the System event raised when a Network Connection
is established in VB.NET (ie. connection from a client to a network
resource, just like the winsock control did successfully for so many years)
AND the one that is raised when data is recieved on this connection. I have
seen many posts suggesting to create a timer and check the network status
(or even use endless loop instead of a timer) but I find this much too
resource hungry for my requirements.
I want to catch the event when it arrises, just like Winsock did or the
event listeners in Java. I know there is a way to do this, I believe it
exists, Microsoft are not the kind of enterprise to start from something
that works well (ie: winsock) and go backward to the flinstone's era (ie:
using an endless loop or a timer to pool again and again and again and eat
all your precious CPU time... The interrupt controler on the PC isn't there
just for the good looking, it have it's purpose and one of them is to "Tell"
that something happened on that or that part pf the hardware, etc.). This
was once implemented and I don't see why this would have disapeared just
like this.
Perhaps I can listen to Windows messages or something like that (if I knew
what to listen for!).
I have tried search MSDN, Google and this newsgroup for a working solution
(Without the loops / timers) but have not been successful.
Any help/code would be greatly appreciated.
Thanks
Nico
I have re-formulated the question I asked on my last post::
I am trying to capture the System event raised when a Network Connection
is established in VB.NET (ie. connection from a client to a network
resource, just like the winsock control did successfully for so many years)
AND the one that is raised when data is recieved on this connection. I have
seen many posts suggesting to create a timer and check the network status
(or even use endless loop instead of a timer) but I find this much too
resource hungry for my requirements.
I want to catch the event when it arrises, just like Winsock did or the
event listeners in Java. I know there is a way to do this, I believe it
exists, Microsoft are not the kind of enterprise to start from something
that works well (ie: winsock) and go backward to the flinstone's era (ie:
using an endless loop or a timer to pool again and again and again and eat
all your precious CPU time... The interrupt controler on the PC isn't there
just for the good looking, it have it's purpose and one of them is to "Tell"
that something happened on that or that part pf the hardware, etc.). This
was once implemented and I don't see why this would have disapeared just
like this.
Perhaps I can listen to Windows messages or something like that (if I knew
what to listen for!).
I have tried search MSDN, Google and this newsgroup for a working solution
(Without the loops / timers) but have not been successful.
Any help/code would be greatly appreciated.
Thanks
Nico