I am using .net remoting with tcp channel and a tcp socket for accepting
connections in a console application. When I run the application first time
everything works fine but if I run the application again I get only one
usage of socket address exception when 'bind' of listener socket is called.
This only occurs if a client is connected to application in the previous
run. Remoting and socket are using different ports, I have also make sure
that socket is closed and tcp channel is unregistered on application
shutdown. Any ideas why listening port remains open ?, I am using .net
framework 1.1.
Re: .net remoting and tcp listener socket ... I am using .net remoting with tcp channel and a tcp socket for accepting ...connections in a console application. ... usage of socket address exception when 'bind' of listener socket is called. ... (microsoft.public.dotnet.faqs)
Re: TcpChannel or HttpChannel ??? ... Be careful with the TCP Channel though, ... Unless you send over lots of objects of the same type in quick succession,... every remoting call will involve opening a new socket on your machine and a ... new socket on the receiving machine, ... (microsoft.public.dotnet.framework.remoting)
Asynchronous Socket Server data ... The socket server knows what type of data it expects due to the interface ... I can have 1 databuffer only for each datatype to handle multiple connections?...int bytesRead = handler.EndReceive; ...packetIndex, bytesRead); ... (microsoft.public.dotnet.languages.csharp)
Re: Ping =?ISO-8859-1?Q?kr=E1ft=E9=E9_=3F_Advice_needed_?= =?ISO-8859-1?Q?to_trace_w ... He has two telephone extensions leading from the master socket and his ... presume that there is a fault in his extension wiring. ... If it's twisted pair ensure that it's not been connected split pair, in other words the blue white with white blue, orange white with white orange, if you get my drift, & the connections you should use are 2&5 ... (uk.telecom.broadband)
Re: !EventConnect Problem ... the June roll-up is available somewhere, although there's not been the usual ... The socket is not in a listening state.... The incoming connection queue has no room for connections.... (microsoft.public.windowsce.app.development)
