Re: Advice on Writing my own socket code vs using MFC built in classes
- From: "Scott McPhillips [MVP]" <org-dot-mvps-at-scottmcp>
- Date: Mon, 23 Feb 2009 16:57:14 -0500
"justmehere" <inderpaul_s@xxxxxxxxx> wrote in message news:4ef88fae-737b-456d-9a85-2ee2d68c7761@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Feb 23, 1:04 pm, justmehere <inderpau...@xxxxxxxxx> wrote:
I have created a MFC based application and now have gotten to the part
of writing the sockets programming part of it. My only question is
should I use the built in classes provided by MFC or should I write my
own. I have read somewhere that using MFC may be more difficult.
Any suggestions or advice would be appreciated.
What I am building in my application is a FTP server. Also the
question is using sockets better with MFC or using Winsock API with my
existing application that is written in MFC ?
CAsyncSocket is reliable and offers a few conveniences over writing your own socket code. If you know enough to write your own winsock code then CAsyncSocket will be quite obvious: It is a rather thin wrapper around async winsock with message notifications. I highly recommend it.
CSocket is a nightmare invention that seems to have been dreamed up by a summer intern who left the company 15 years ago.
--
Scott McPhillips [VC++ MVP]
.
- References:
- Advice on Writing my own socket code vs using MFC built in classes
- From: justmehere
- Re: Advice on Writing my own socket code vs using MFC built in classes
- From: justmehere
- Advice on Writing my own socket code vs using MFC built in classes
- Prev by Date: Re: Passing a reference to a std::map
- Next by Date: Re: Passing a reference to a std::map
- Previous by thread: Re: Advice on Writing my own socket code vs using MFC built in cla
- Next by thread: Re: Advice on Writing my own socket code vs using MFC built in classes
- Index(es):
Relevant Pages
|
