Beyond MFC : COM || Networking

Hi.

I began learning and practice MFC three months ago. The first month was the toughest because I was down right lost after reading the first nine chapters from Prosise's book. However, everything changed after I first studied from Richand Jones' introduction to MFC. Everything Prosise discusses became clear and only now do I begin to appreciate the information Prosise offers in his book.

Next, I would like to move on to more specific tools i.e. networking or COM. I have no experience with COM and networking programming using C++. My ultimately goal, however, is to design and implement network programs such as an ftp server (my dream).

What is there after MFC? I am an MFC beginner, but I have confident I can work with the tools MFC offers relatively well.

I am very interested in networking programming, but COM is something that is quite popular. I saw good review on C++ Networking Programming Volumn 1 by Douglas C. Schmidt, Stephen D. Huston. What do you recommend? As for COM, I am not sure where to start. Nonetheless, COM is something I want to consider, if not now, then after networking.

Thanks,
Kuphryn

Hello, I never botherd with MFC and just went into Windows. Very easy once you know it. Would I be wrong in saying you wasted your time learning MFC, maybe, maybe not.

But anyways, now you want to learn network programming, well I can say this, it's very easy when you know it! But with network programming we use sockets. When programming sockets for windows, we usually call it "Winsock" for short. When you begin to learn sockets, you will most likely start with non-blocking sockets, that is, functions wait for what it wants and this disallows anthing else in this thread to happen, you could use threads and have multiple threads but this is sh!t. When programming with sh!t sockets for the Windows console or younicks or whatever, these things and technically called BSD sockets. BSD = Burkly socket dope or something like that. Anwyays, what you want to do is use non-blocking sockets cos these are much better than blocking sockets. When using non-blocking sockets, you use fuction select() for BSD and WASYSelect() fo windows. Only with non-blocking sockets will you be cool.

Lastly, some words of wisdom. Programmers can't remember all the functions and everything at msdn and every little sh!t there is to know. I think the programmer should always have a reference.

BTW, ftp servers ar'nt that hard, infant's stuff.

I'll give you an estimate for the time you'll be learning: 1 to 3 years.

Have fun!

Thanks.

I give you credit for your success with Windows programming via Win32 API. I honestly I have make an attemp to learn Win32 API. I do admit that the examples I have seen makes me want to continue using MFC. I believe there is a line between too many things to master, and that where how I see Win32 API right now.

I have some key references for both C++ and MFC. I have not set step into network programming, so that is something that will occur soon.

As for the 1-3 years learning time, I definitely see your point. It is very much conceivable. I will tried all in my power to get something going as quick as possible (6 months). Do not take that as a challenge though. I am sure networking programming deals directly with Win32 API. Win32 API will take some getting used to.

Kuphryn

I have the first edition of this

The writers are M$ developers....they cant write very well, but they seem to know their ..........!!!

As to time wasting with MFC...I disagree......

I learned some WinAPI first and then went into MFC......I still use WinAPI for smaller things, testing and when MFC doesnt offer something too easily......but if I want to try something bigger I tend to start with MFC as a base.........

BTW....if I ever use any network programming, I prefer the Winsock API as opposed to the socket wrappers that MFC offers.......sometimes I can get away with this........

Okay.

I am considering C++ Networking Programming Volumn 1 by Douglas C. Schmidt, Stephen D. Huston, which goes over networking programming using ACE library. I am not familiar of ACE library and how it relates to MFC.

Kuphryn

Okay.

I decided on a network programming book.

I placed on order for this:

Network Programming for Microsoft Windows, Second Edition
by Anthony Jones.

I have considered C++ Network Programming Volume 1 by Douglas C. Schmidt and Stephen D. Huston. However, in the end I decided to go with Networking Programming for Microsoft Windows, Second Edition because my primary objective is to design and implement Windows programming using C++. I believe Jones' book will become invaluable for Windows applications.

Kuphryn