.NET Forum / .NET Framework / New Users / May 2004
WSAAsyncSelect in .Net framework
|
|
Thread rating:  |
Vladimir Scherbina - 29 May 2004 21:54 GMT hello all,
is thery any equivalent in .Net Framework of WSAAsyncSelect win32 api function ? I want my application window being notifyed about network events... (asyncroniously)
or maybe another way exists ?
-- Vladimir Scherbina, Ukraine, Kiev.
Yuancai \(Charlie\) Ye - 30 Apr 2004 14:07 GMT hi, No! dotNet framework losts all of WSAXXX api functions. However, my SocketPro has it.
 Signature Yuancai (Charlie) Ye
Fast and securely accessing all of remote data sources anywhere with SocketPro using batch/queue, asynchrony and parallel computation
See 30 well-tested and real OLEDB examples
RDB, a tool for fast and securely accessing remote databases with dial-up, cable, DSL and wireless modems anywhere www.udaparts.com
> hello all, > [quoted text clipped - 8 lines] > Vladimir Scherbina, > Ukraine, Kiev. William Stacey [MVP] - 30 Apr 2004 17:42 GMT Why not do Socket.Select in another thread and report back to application window using one of many options (push/pull, etc) Think you do pretty much what you want via some design work. Post back if other questions of this. Cheers!
 Signature William Stacey, MVP
> hello all, > [quoted text clipped - 8 lines] > Vladimir Scherbina, > Ukraine, Kiev. Vladimir Scherbina - 31 May 2004 09:34 GMT hello William, sure, Socket.Select is another way of solving my problem, but imagine, if i have for example 1000 cleints and 1 server, each client is accepted by server. server has 1000 sockets, in the way you propose server should call Select for each socket at some time on a loop... but this architecture is looking strange (as for me) i am wrong ?
-- Vladimir Scherbina, Ukraine, Kiev.
> Why not do Socket.Select in another thread and report back to application > window using one of many options (push/pull, etc) Think you do pretty much [quoted text clipped - 3 lines] > -- > William Stacey, MVP William Stacey [MVP] - 01 May 2004 16:17 GMT Now you say 1000 :-) IIRC, when your talking about the Async methods (Begin..), your talking Thread pool. I am wondering if you will have fairness issues here or other issues relating to the thread pool. Not sure. If you have a dedicated machine you can probably get 700-800 threads without a problem and simplify your implementation dramatically. I know it sounds crazy, but had a long talk with the Indy .Net guy about this and he was right and it works. The cpu will handle fairness via normal thread scheduling. You may also want to checkout the Indy .Net library for socket stuff. They also can use Fibers to allow more connections.
 Signature William Stacey, MVP
> hello William, > sure, Socket.Select is another way of solving my problem, but imagine, if i [quoted text clipped - 17 lines] > > -- > > William Stacey, MVP Chris Botha - 30 Apr 2004 20:57 GMT Look at all the "Begin..." and "End..." functions in sockets, for example BeginConnect, BeginAccept, BeginSend, BeginReceive, etc, these are all async functions. You won't get the socket close directly, but if you issue or have an outstanding read/write, etc, you will realize that in the handler routine.
> hello all, > [quoted text clipped - 8 lines] > Vladimir Scherbina, > Ukraine, Kiev. Vladimir Scherbina - 31 May 2004 09:26 GMT thx, i lave looked and i use them
-- Vladimir Scherbina, Ukraine, Kiev.
> Look at all the "Begin..." and "End..." functions in sockets, for example > BeginConnect, BeginAccept, BeginSend, BeginReceive, etc, these are all async [quoted text clipped - 14 lines] > > Vladimir Scherbina, > > Ukraine, Kiev. Teemu Keiski - 01 May 2004 10:56 GMT Please, check also your machine's time settings.
 Signature Teemu Keiski MCP, Microsoft MVP (ASP.NET), AspInsiders member ASP.NET Forum Moderator, AspAlliance Columnist http://blogs.aspadvice.com/joteke
thx, i lave looked and i use them
-- Vladimir Scherbina, Ukraine, Kiev.
> Look at all the "Begin..." and "End..." functions in sockets, for example > BeginConnect, BeginAccept, BeginSend, BeginReceive, etc, these are all async
> functions. You won't get the socket close directly, but if you issue or have
> an outstanding read/write, etc, you will realize that in the handler > routine. [quoted text clipped - 11 lines] > > Vladimir Scherbina, > > Ukraine, Kiev.
Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
|
|