C / C++ / MFC

17-Mar-03 12:18

This should be a simple one for everyone:
I have written a simple client server app to read in a string and send it across. I have implemented this with standard CSockets but want to port it in a simple manner to use CAsyncSockets. I am not familiar with the sequence of events that occur with these-I only know how the CSockets work:

Client<br />
create<br />
connect(IP,Port)<br />
//using archive<br />
CArchive.write(...)<br />
//then tidy up<br />
<br />
Server<br />
create(Port)<br />
listen<br />
//using archive<br />
CArchive.read(...)<br />
//then tidy up

I know that the asyncs. don't use archives and that the read and write mechanisms are different; but the more serious problem that I have is that I have no idea how things are meant to be ordered. I have read a lot about overloading member functions and the like but am thoroughly confused. Anyone able to offer some hints? I have read and tried to disassemble the code for the AsyncProxySocket example that's on here somewhere and ended up bashing my head against the wall. Confused | :confused:

There doesn't seem to be a great deal in the msdn about them. Eek! | :eek:

Thanks in advance

Florin Ochiana17-Mar-03 12:55

Florin Ochiana

17-Mar-03 12:55

Hi,

Read this: http://www.codeproject.com/internet/winsockintro01.asp
And check into the Internet Section. There are other articles related to your problem.

-----
We are what we repeatedly do. Excellence, then, is not an act, but a habit.

Moak18-Mar-03 1:40

18-Mar-03 1:40

I suggest taking a look into existing source code using CAsyncSocket ( e.g. older Gnucleus code).

The client side is pretty less work, but the server side has to take care about incoming socket and e.g. cleaning up socket objects when they die.

chrisedgington18-Mar-03 23:18

18-Mar-03 23:18

Thanks for taking the time to reply. I have attempted to go through some of the other code that uses the Async sockets, but I can't seem to follow what's going on. If I want to use them, I need to be able to override the OnAccept() and OnSend() etc. member functions; but when are these called?
If I define my own class derived from CAsyncSocket and override the member functions, what is the order of events that must occur for these functions to work?

<br />
class Mysocket : public CAsyncSocket<br />
{<br />
public:<br />
virtual void OnAccept(int nErrorCode);<br />
virtual void OnClose(int nErrorCode);<br />
//OnSend, OnReceive, OnConnect here too<br />
}<br />
<br />
Mysocket::OnAccept(int nErrorCode)<br />
{ //when will it get to here?:confused:<br />
SleepEx(1000,FALSE); //just for illustration purposes<br />
CAsyncSocket::OnAccept(nErrorCode);<br />
}<br />

Say for instance that I have a function in an mfc document class that is meant to do the job of recieving, its code currently looks like this: (this code is what I have ported from a CSocket version which is why it looks a little funny)

<br />
int CAsyncItDoc::RecieveStuff()<br />
{<br />
int status =0;<br />
Mysocket Myskt;<br />
char theString[4096];<br />
if(Myskt.Create(5001) == 0) //create socket<br />
{<br />
status = Myskt.GetLastError();<br />
return status;<br />
}<br />
if(Myskt.Listen() == 0) //listen on socket<br />
{<br />
status = Myskt.GetLastError();<br />
return status;<br />
}<br />
Mysocket theRec; //new socket to pass call onto<br />
if(Myskt.Accept(theRec) == 0) //accept call (should this be here?):~ <br />
{<br />
status = Myskt.GetLastError();<br />
return status;<br />
}<br />
//////////////<br />
//this is the i/o bit -> should this be here?:~ <br />
ofstream outfile;<br />
outfile.open("igotthis.txt");<br />
while (theReciever.Receive(theString,4096) != 0)<br />
{<br />
outfile << theString <<endl;<br />
status++;<br />
}<br />
//////////////<br />
//tidy up-> maybe this should be in Onclose()?:~ <br />
outfile.close();<br />
Myskt.Close();<br />
return status;<br />
}<br />

I realise this sounds awfully lazy but some of the other code uses CDialogs which I've never used, and all the overridden member functions end up really long and complex. All I'm after is a simple implementation and at the moment all I have is a good way of getting confused.
Thanks for any (further) advice. Smile | :)

Moak19-Mar-03 3:36

19-Mar-03 3:36

Yes, you basically will override a few member functions. Remember, asynchronous sockets will not be polled or go into blocking mode... instead you get an event when something interesting happens and can handle it. For example OnConnect() will be called after a succesfull or failed Connect() call, have a look on examples.

chrisedgington19-Mar-03 4:31

19-Mar-03 4:31

Thanks Moak-I was failing to get the thing to accept a call properly but have cheated now:

<br />
while(true)<br />
{<br />
if(Myskt.Accept(RecSock)==0)<br />
{<br />
SleepEx(10,FALSE);<br />
}<br />
else<br />
{ <br />
//when it hits here the call should have been accepted<br />
//and onaccept called, right?<br />
Myskt.Onaccept(); //but i am having to do it manually <br />
break;<br />
}<br />

This is my OnAccept() function as it stands. The function doesn't seem to call it automatically when the if condition is not 0 (i.e the accept completes); instead I am invoking it manually. Can you see what it is that I am doing wrong?

<br />
void Mydamnsocket::OnAccept(int nErrorCode) <br />
{<br />
Mydamnsocket RecSock;<br />
Mydamnsocket::Accept(RecSock);<br />
char Acceptmsg[20]="Connected to server";<br />
Mydamnsocket::Send(Acceptmsg,20);<br />
} <br />

Is it necessary to stick another thread in to deal with this or something?
Unsure | :~

P.S. You mention about reading the examples section-can you recommend a particular one that contains an implementation of this that isn't too complex? Cheers!

Moak19-Mar-03 4:47

19-Mar-03 4:47

Sorry, I dont have the time at the moment to search for a good example... actually I tried and didn't find one. Hmm, I remember that old Gnucleus code (1.4.x) used class CAsyncSocket and was a good starting point.
Some notes: You will not call OnAccept() manually, instead wait for it to be called. CAsyncSocket will handle everything in one thread context. So basically there's no need for polling, sleeping, multithreading with it.

Here is a little snippet from my code:

// New socket tries to connect to server's listening port
void CSocketServer::OnAccept(int nErrorCode) 
{				//maximum number of sockets reached (prevent DoS)
	if(m_nNodesConnected >= m_pref.m_nMaxSockets) return;
				//create a new node socket	
	CSocketNodePICHAT* pSocket = new CSocketNodePICHAT(this);
	if(Accept(*pSocket))	//accept incoming socket and connect to node socket
	{
		pSocket->SetStatus(SOCKET_CONNECTED);
		m_NodesList.push_back(pSocket); //add socket to internal list
		m_nNodesConnected++;
	} else {			//catch socket errors
		pSocket->SetStatus(SOCKET_DEAD);
		delete pSocket;
	}
}

// PS: Don't forget to delete closed sockets from your m_NodesList.

Hope it helps Smile | :)

chrisedgington19-Mar-03 4:58

19-Mar-03 4:58

Ah ha-I can hear the penny finally beginning to drop Smile | :)

Thanks for that. One thing though, say I have a simple app that starts my recieve function off when the user hits a button, and this creates a socket and starts to listen to the port. I realise now that onaccept will be called automatically when the client wants to connect to it on the right port#, but what do I do in the rest of the function? Should I simply set up the socket and make it listen; have my function return and then wait... then the program will do the job automatically? I take it that the rest of the functions get called automatically as well once the appropriate event occurs?
(I feel like I'm answering my own questions here-I hate it when that happens Wink | ;)

)
Thanks again for your help-I appreciate you've got better things to do. I'll let you have a metaphorical beer for all your efforts Big Grin | :-D

Moak19-Mar-03 5:08

19-Mar-03 5:08

chrisedgington wrote:
I take it that the rest of the functions get called automatically as well once the appropriate event occurs?

yup. fire your stuff and handlers will be called when necesarry.

Thanks for the Beer | [beer]

, cheers!

chrisedgington19-Mar-03 6:07

19-Mar-03 6:07

That's ok. You sir have been a great help. If you feel like helping more; you might like to tell me why OnAccept and my other member functions are not being called? I have set up a beginsend and a beginreceive function in the document class, which do the following:

beginsend:

<br />
{<br />
        int status=0;<br />
	//Used for debug<br />
	Mydamnsocket Myskt;<br />
	//Creates an AsyncSocket object<br />
	int nPort = 5001;<br />
	//Specifies the port number to connect to<br />
	CString IPAddy="127.0.0.1";<br />
	//Creates a CString object with address<br />
	Myskt.Create();<br />
	//Creates a socket<br />
	Myskt.Connect(IPAddy,nPort);<br />
        //Connects the socket<br />
        return status;<br />
}<br />

beginrecieve:

<br />
{<br />
        int status = 0;<br />
	//Used for debug<br />
	Mydamnsocket Myskt;<br />
        //creates a socket<br />
        Myskt.Create(5001);<br />
        //turns the socket to port # 5001<br />
        Myskt.Listen();<br />
        //makes the bugger listen<br />
        return status;<br />
}<br />

So the user kindly runs up two of these apps and hits recieve in one and send in the other-thus calling these functions. If I watch developments in the Debugger with a few cleverly placed breakpoints (well actually, every darn line at the moment), I would expect to see the program jump into my Mydamnsocket class and the onaccept member function; but it doesn't-it just sits there. This is somewhat puzzling and is stopping me from getting anywhere. Once I can get the functions called I should pretty much be there with this.
Plenty Smile | :)

beer for you if you can help?

Win 32 Tooltip

Anonymous17-Mar-03 12:18

Anonymous

17-Mar-03 12:18

Can anyone help me out a little with my tooltip under Win32?

I have created the control (called InitCommonControlsEx also) and filled in my TOOLINFO struct like so:

<br />
// Initialize ToolInfo Struct<br />
ti.cbSize = sizeof(TOOLINFO); <br />
ti.uFlags = TTF_IDISHWND; <br />
ti.hwnd = hwnd; <br />
ti.hinst = hInst; <br />
ti.uId = (UINT) hwndView; <br />
ti.lpszText = (LPSTR) szTool;<br />

hwndView is an owner drawn button btw

Then I added the tool with this message:

<br />
SendMessage(hwndTool, TTM_ADDTOOL, 0, (LPARAM) (LPTOOLINFO) &ti);<br />

and I subclassed the button control and processing the WM_MOUSEMOVE message I sent the following message:

<br />
SendMessage(hwndTool, TTM_RELAYEVENT, 0, (LPARAM) (LPMSG) WM_MOUSEMOVE);<br />

Unfortunately as soon as the mouse enters the button's window the program crashes. What am I missing here? Some help or a link to some other code examples would be much appreciated. Thanks.

Neville Franks17-Mar-03 17:44

Neville Franks

17-Mar-03 17:44

There isn't much I can tell from looking at this code. The first thing I would do is run the Debug build and inspect the crash in the debugger and work back from there.

Neville Franks, Author of ED for Windows. www.getsoft.com
Make money with our new Affilate program

georgiek5017-Mar-03 22:46

georgiek50

17-Mar-03 22:46

In Debug mode, as soon as I move the window over the control it crashes with the well know message:

Unhandled exception in ToolTest.exe (COMCTL32.DLL) 0xC0000005: Access Violation

with the yellow pointer pointing to this line:

77365F4F push dword ptr [eax+0Ch]

Unfortunately I am not to good at interpreting the debugger.

I have only posted this code because that is basically all I have. I am confused about whether or not I need a special CALLBACK function to take care of the TTM_RELAYEVENT message or is it handled internally by Windows?

P.S. I have neither set a timer or a hook for relaying of messages

Neville Franks17-Mar-03 23:35

Neville Franks

17-Mar-03 23:35

I don't think you want nor need:

SendMessage(hwndTool, TTM_RELAYEVENT, 0, (LPARAM) (LPMSG) WM_MOUSEMOVE);

Have you tried removing this.

Also add:

memset( &ti, 0, sizeof( TOOLINFO ) );

before: ti.cbSize = sizeof(TOOLINFO);

Have a search around CP for articles which use Tooltips.

Neville Franks, Author of ED for Windows. www.getsoft.com
Make money with our new Affilate program