Re: MFC: TCP/IP and Serialization

The MFC serialization is a framework for doing this if (and only if) all of=
 the classes and subclasses you are using are derived from CObject. Each su=
ch class has a Serialize method. To serialize a complex class you must over=
ride its Serialize method and invoke the Serialize method of all its sub cl=
asses. So it is a "framework" but not a total solution.

The advantage MFC's framework gives you over doing everything yourself is t=
hat MFC has already defined the "custom format" that is used in the message=
s. So you don't have to do the formatting and de-formatting part. But you d=
o have to write the Serialize method for every class and sub class that has=
 multiple data members.

For an example of doing this see the MFC sample DRAWCLI in the MSDN library=
..

The speed of serialization is going to be about the same whether you use yo=
ur own format or MFC's. It's an inherently low-level process that must deal=
 with everything byte-by-byte.

Another possible solution might be to use a separate thread instead of a se=
parate process. With a "server thread" you do not have to do serialization =
at all since both threads can access the same data structures.