Article View: borland.public.cppbuilder.internet.socket
Article #5589Re: Indy TIdTCPServer creation at untime
From: J�nior B. Dymow
Date: Fri, 16 Jul 2004 21:13
Date: Fri, 16 Jul 2004 21:13
62 lines
2819 bytes
2819 bytes
> > The point is: creating the TIdTCPServer object
> > dinamically doesn't works.
>
> Yes, it does, when used properly.
That's what I'm looking for: the correct way to use it...
>
> > When I connect a client application, the answer I have is:
> > "No connection could be made because the target machine
> > refused it (10061), on API 'connect'
>
> Did you set up any Bindings first?
No, I didn't. Can you please tell me how to do it? But I didn't
do it with the design time component, and it worked. Do you think this can
be the problem?
> > When the component is on the form (with the same port,
> > and the same OnExecute function assigned), it works fine.
>
> There is no difference between creating the component at design-time vs.
> run-time, other than the DFM streaming.
>
>
> Gambit
>
>
=======================
J�nior B. Dymow
Desenvolvimento
Specto Pain�is Eletr�nicos
junior@specto.com.br
Fone / Fax: (48) 334-8064
=======================
"Remy Lebeau (TeamB)" <gambit47.no.spam@no.spam.yahoo.com> escreveu na
mensagem news:40f83fb3$1@newsgroups.borland.com...
>
> "J�nior B. Dymow" <junior@specto.com.br> wrote in message
> news:40f83bb1$1@newsgroups.borland.com...
>
> > The point is: creating the TIdTCPServer object
> > dinamically doesn't works.
>
> Yes, it does, when used properly.
>
> > When I connect a client application, the answer I have is:
> > "No connection could be made because the target machine
> > refused it (10061), on API 'connect'
>
> Did you set up any Bindings first?
>
> > When the component is on the form (with the same port,
> > and the same OnExecute function assigned), it works fine.
>
> There is no difference between creating the component at design-time vs.
> run-time, other than the DFM streaming.
>
>
> Gambit
>
>
Technical Details
Message-ID:
<40f84444@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news.maxwell.syr.edu!logbridge.uoregon.edu!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mailReferences:
<40f822f9@newsgroups.borland.com> <40f831be$4@newsgroups.borland.com> <40f83bb1$1@newsgroups.borland.com> <40f83fb3$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,245bc6439db2ac9c X-Google-Attributes: gid11508e,public X-Google-Language: ENGLISH,ASCII From: "J�nior B. Dymow" <junior@specto.com.br> Newsgroups: borland.public.cppbuilder.internet.socket References: <40f822f9@newsgroups.borland.com> <40f831be$4@newsgroups.borland.com> <40f83bb1$1@newsgroups.borland.com> <40f83fb3$1@newsgroups.borland.com> Subject: Re: Indy TIdTCPServer creation at untime Date: Fri, 16 Jul 2004 18:13:06 -0300 Lines: 64 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 NNTP-Posting-Host: 200.135.30.176 Message-ID: <40f84444@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1090012228 200.135.30.176 (16 Jul 2004 14:10:28 -0700) Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news.maxwell.syr.edu!logbridge.uoregon.edu!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail