Newsgroups : Borland : borland.public.delphi.internet.winsock : 2008 Feb : Indy 10 TIdIRC component problems.

www.cryer.info
Managed Newsgroup Archive

Indy 10 TIdIRC component problems.

Subject:Indy 10 TIdIRC component problems.
Posted by:"Unspoken" (ff_aa_cc_ee_..@wp.pl)
Date:Wed, 6 Feb 2008 22:05:36

Hi.

First of all I wanted to thank for pointing me out for this component
instead of TIdTCPClient. It works pretty well in most cases..
However I have two problems compared to the TIdTCPClient:

1. I've noticed that each time server sends something to my client, TIdIRC
automatycially responds with message "200".
However the server is not 100% compatible with RFC IRC protocol and it
doesn't recognize command "200" as "OK" and each time returns information
about unknown command. How to prevent TIdIRC from sending this message? I
was reading source and if I am not wrong the solution is in
TIdComandHandlers and TIdReplyRFC however it is a lot of code to
understanding.. Any advice how to solve this?

2. When I was using TIdTCPClient.IOHandler.Readln method I had every
messages from the server. When I am using TIdIrc.OnRaw event, not every
message from the server seems to get through. For example the PING command
to my client is somewhere earlier intercepted (I assume that it is
intercepted by the TIOhandler but where?) and I can't respond on it.

Maybe this is caused becuase I have to connect on different port (5579)
instead of 6667 and I saw in the source that some constants define port 6667
as a main IRC port.

Thanks for any help,

Regards.

Replies:

www.cryer.info
Managed Newsgroup Archive