Hi there...

I want to write a small utility.
It should be front- and backend running on different machines.

I don't want to handle error correction or timeouts by myself.
Communication is TCP/IP.

How could I easyly do the communication?
CSocket or something else.

Thanks in advance

Stefan

Re: Client Server using TCP/IP - which interface to use? by Heinz

Heinz
Thu Jul 21 15:46:51 CDT 2005

"Stefan Kittel" <stefan.doofnase.kittel.NoSpam@web.de> schrieb im
Newsbeitrag news:OFsMb9ijFHA.2644@TK2MSFTNGP09.phx.gbl...
> Hi there...
>
> I want to write a small utility.
> It should be front- and backend running on different machines.
>
> I don't want to handle error correction or timeouts by myself.
> Communication is TCP/IP.
>
> How could I easyly do the communication?
> CSocket or something else.

CSocket and CAsyncSocket are reasonable solutions for the frontend. On the
backend (server side) you might want to avoid the overhead of including MFC
and use sockets directly. If you are interested, I can send you a simple
socket class that does not use MFC. (Remove .SPAM from adress.)

HTH
Heinz



Re: Client Server using TCP/IP - which interface to use? by Stefan

Stefan
Fri Jul 22 04:13:31 CDT 2005

Hi...

With CSocket I had several problems before.
detect timeout
missing data
I used IFF Segements to solve this

isn't there something better and easier to use?

Stefan


"Heinz Ozwirk" <hozwirk.SPAM@arcor.de> schrieb im Newsbeitrag
news:42e009bb$0$21249$9b4e6d93@newsread2.arcor-online.net...
> "Stefan Kittel" <stefan.doofnase.kittel.NoSpam@web.de> schrieb im
> Newsbeitrag news:OFsMb9ijFHA.2644@TK2MSFTNGP09.phx.gbl...
>> Hi there...
>>
>> I want to write a small utility.
>> It should be front- and backend running on different machines.
>>
>> I don't want to handle error correction or timeouts by myself.
>> Communication is TCP/IP.
>>
>> How could I easyly do the communication?
>> CSocket or something else.
>
> CSocket and CAsyncSocket are reasonable solutions for the frontend. On the
> backend (server side) you might want to avoid the overhead of including
> MFC and use sockets directly. If you are interested, I can send you a
> simple socket class that does not use MFC. (Remove .SPAM from adress.)
>
> HTH
> Heinz
>