I was wondering why server not have cocreate instance in second thread. Because you know, like em these things, you cannot have thread in threads without code in middle somewhere. Doing so will not work, should not work. I code for many moonfaces white men and they say curry can't code, but I say unto them curry can code yes.
This topic is very much usefull but when I am tring callback from vb client it give error like "can't read from memory location ...".I am doing a project with com with callback support.If any knows the solution please help me.
After reading the article I tried to make a connectable object.The object was succesful since I tried it with a VB Client.But my VC++ client didnt work(I think the dispatch parameter is not getting assigned any value)
Please try to solve this problem.
In your presentation, you said that if we include CallBack.idl in the client side, we should be OK. Unfortunately, we aren't OK, because I simply did not manage to make my server (MFC server with ATL support) send any notifications back to my client ( which is based on MFC with ATL support). You probably ignored to present some very important steps in defining the ICallBack interface, because just following your presentation, we get nowhere.