Article View: borland.public.cppbuilder.internet.socket
Article #5543Client Socket Connect Question
From: OKusmen
Date: Tue, 03 Aug 2004 08:20
Date: Tue, 03 Aug 2004 08:20
10 lines
1538 bytes
1538 bytes
I use TClientSocket. I want to get help about this component working. I want to send messages. First message is for a host that is not available in the network now. After my connection request, connection error event occurs(eeLookup errorcode). This is normal situation that I expect. After this event, I want to send another message to another client that is available in the network. I expect that connection event occurs, but does not. Again, error event occurs with eeConnect error code. I try this message to same host again. This time, connection is established. In this scenario, I have to try a message two times. But, I want to try once. What reason occurs this situation.
Technical Details
Message-ID:
<410f4afe@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!zen.net.uk!dedekind.zen.co.uk!news.zanker.org!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Thread: 11508e,5e7c9fcee6f0909e,start X-Google-Attributes: gid11508e,public X-Google-Language: ENGLISH,ASCII-7-bit From: "OKusmen" <okusmen@aselsan.com.tr> Newsgroups: borland.public.cppbuilder.internet.socket Subject: Client Socket Connect Question Date: Tue, 3 Aug 2004 11:20:03 +0300 Lines: 12 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 NNTP-Posting-Host: 212.50.56.195 Message-ID: <410f4afe@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1091521278 212.50.56.195 (3 Aug 2004 01:21:18 -0700) Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!zen.net.uk!dedekind.zen.co.uk!news.zanker.org!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail