Newsgroups : Borland : borland.public.delphi.internet.winsock : 2005 Nov : System.Net.Sockets.TcpClient <---> Indy

www.cryer.info
Managed Newsgroup Archive

System.Net.Sockets.TcpClient <---> Indy

Subject:System.Net.Sockets.TcpClient <---> Indy
Posted by:"RGreen" (rgreen@nospam.org)
Date:Thu, 1 Dec 2005 00:26:46

Hello!

I am  working in a .net project which uses clean
System.Net.Sockets.TcpClient sockets. It needs to communicate with a simply
server which uses win32 indy 10.

The server expects a string. It uses:

s:= idTCPServer.Connection.IOHandler.Readln();

and sends a response

idTCPServer.Connection.IOHandler.WriteLn(somestring);

So, how can I make System.Net.Sockets.TcpClient to clearly communicate with
the server? What I am unsure is the fact that .net uses widestrings and
indy10 (win32) uses ANSI.

So i am searching for 2 .net procedures;

procedure SendString(const s:string);
begin
    // using System.Net.Sockets.TcpClient
    //???
end;

and

function GetString(): string;
begin
//System.Net.Sockets.TcpClient
//???

end;

Some help?

Replies:

www.cryer.info
Managed Newsgroup Archive