Re: Regarding CArchive,Files and CSockets
I agree with Scott. I use XML formatted packets so that they can easily be
written to a disk (log) file when I want to see what's happening with the
flow, but I'd stay away from CArchive for this kind of purpose and just go
with CAsyncSocket.
You may find this write up to be a good start:
http://msdn2.microsoft.com/en-us/library/t7a47kk4(VS.80).aspx
Tom
"James Simpson" <JamesSimpson@discussions.microsoft.com> wrote in message
news:81B75D88-F3C1-431A-AB71-5A57F80AC302@microsoft.com...
Hello again,
I am trying to work on creating the client/server portion of my solution
via
MFC. I think I got a handle on threading and sockets a bit so far.
Essentially each connection on the client/server side uses this type of
code:
CSocket CurSocket;
CurSocket.Create();
CSocketFile CurSocketFile(&CurSocket,TRUE);
CArchive arSend(&CurSocketFile,CArchive::store);
CArchive arRecv(&CurSocketFile,CArchive::load);
CurSocket.Connect("localhost",1337);
(e.g. it creates a socket if it doesn't have one, and attaches the
CSocketFile and CArchive classes to allow data to be streamed into out of
the
socket). I can send a CString and some basic data types by simply using
<<
and calling flush afterwards to send the data and use >> on the receiving
end
to receive the data. The problem that I have, however is sending files
using
CArchive interface. How do you use CArchive to send the data to the
server
or client?
Regards,
James Simpson
Straightway Technologies Inc.