Raj Prathap wrote: Please confirm whether 'if' could be placed inside a switch statement. Why would you go to all the trouble of creating this post when you could have just compiled it to find out? :rolleyes: "Love people and use things, not love things and use people." - Unknown "To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

Read with one thread and write with another is fine with one proviso. If you're unfortunate enough to be using MFC Sockets then don't pass the handles (Which are actaully Window Handles) between threads lest they suddenly and magically become invalid. It can be done but you'll need to root around in the MS Docs to find how to do it safely. If you're writing this sort of thing you might want to check out IO Completion Ports, a bit mind bending but they can make multithreaded socket apps a lot slicker. :) Nothing is exactly what it seems but everything with seems can be unpicked.

:-D If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.

jhwurmbach wrote: 0. No elements would be retrievable. Why sould the "GetSize"-function answer a question other than that "How many elements are in the collection?". There are no elements to be retrieved, so the answer is [zero]. The number of elements that are in a collection is not the same as the number of elements that are retrievable/available.  GetSize() vs. GetAvailable().  The lot at the Aston Martin dealership contain 87 cars, but zero of them are available to me! :laugh:    This is becoming a pointless argument :) - you will recall in my OP that I mention the words "poor design".  And I have seen lots of poor designs and heard many ways of defending/rationalizing them.    Peace! -=- James Please rate this message - let me know if I helped or not! * * * If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong! Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road! See DeleteFXPFiles

You are welcome :-D If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.

I Tried with BSTR**, could not succeed. Only first string comes, since the marshaller considers only the first string, since length is not mentioned. I got a hint from one of CP members to use SAFEARRAY(BSTR)* that worked fine.

Thanks a ton Mike, working and its very easy to code.

It's a little while since I did any COM connection points but if your data isn't getting through then I guess it's a marshalling issue. Check you Proxy/Stub implementation. Parameters in the event notifications should definitely work. The Server end needs a loop to notify all the clients for each event. Most of the samples leave this out as they simplify to one client. 5 years ago I had to implement reverse connection points with no documentation so I remember how painful this can be.;) Nothing is exactly what it seems but everything with seems can be unpicked.

The problem got soleved. We have to make the server free threaded and make the class implementing the interface singleton and we need to in _tWinMain.. make sure that CoInitializeEx gets called. Just trial and error caused a break through. Thanks and regards, Raja Pratap

Naveen.R wrote: eg for( int nIdx =0;nIdx<100;nIdx++) { ... } 1. Put a break point in the next line after for loop. 2. Take the breakpoint window( uner the edit menu or press ctr + B ) 3. select the break point you put in the for loop 4. Press the "condition" button. 5. In the new dialog box apperared enter put nIdx>=50 Another suggestion is... #ifdef _DEBUG #define DBREAK( condition ) if(( condition )){ _asm int 3; } #else #define DBREAK( condition ) #endif for( int nIndex = 0; nIndex < 100; ++nIndex ) { DBREAK( nIndex == 50 ) } Nibu thomas A Developer Code must be written to be read, not by the compiler, but by another human being. http:\\nibuthomas.wordpress.com

led mike wrote: "Code Project... best entertainment value on the Web!" :laugh: !! I came close to opening that can of worms (the link) :) "Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

Raj Prathap wrote: My doubt is is there any way to send the notification from the server to all the clients? and also can the server select the client to which it has to send the notification. It's not clear to me what you mean by "chat server" and "notification". When someone talks about a chat server to me I interpret it as the MSDN sample CHATTER/CHATSRVR[^], but the notification you're talking about feels like a callback on a source interface from a COM server to its client (AKA a COM event). If the notification is a COM event, the answer is that the server keeps track of its clients in a container; a list, vector or array. When an event is generated the container is walked through notifying all registered clients. If you want to skip one of the clients you have to write your own code to do that. A small thought: You don't have to use the connection point concept, in fact Don Box recommends not to use it in his book Effective COM[^]. You can create your own Advise() method and put whatever functionality in it that you want and/or need. But if you're new to this it could be a good starting point using the connection point concept to understand how it works. "It's supposed to be hard, otherwise anybody could do it!" - selfquote "High speed never compensates for wrong direction!" - unknown

Thanks Pallini, That answers my question.

Its interesting I think your answer yesterday but I dont know its on edit section or button section on the codeproject ;) WhiteSky

Stack traces of what the application is doing when hung would be a big help. Also, what framework (if any) is being used? Steve

1. The reason why the message box doesn't pop up when you're building for release is probably that it is generated from an ASSERT and the ASSERT macro is disabled when building for release. 2. If you mix a debug-built DLL with a release-built application and you allocate memory in one of them and deallocates it in the other, you will get into troubles. Not only because it is suspect design, but because the memory checking gets screwed up when it checks for boundaries and how much is allocated for each block. 3. Make sure you're linking with the debug-built libraries when building for debug. 4. If none of the above applies to your situation, post again and describe your problem some more. It would be of great help to know where your application crashes and what the call stack looks like at that point. -- Roger "It's supposed to be hard, otherwise anybody could do it!" - selfquote "No one remembers a coward!" - Jan Elfström 1998 "...but everyone remembers an idiot!" - my lawyer 2005 when heard of Jan's saying above

Raj Prathap wrote: In the above case should the destructor of A be called explictly? No. It will happen automatically when the A object goes out of scope. "Approved Workmen Are Not Ashamed" - 2 Timothy 2:15 "Judge not by the eye but by the heart." - Native American Proverb