Thread and Event problem

Question

0.00/5 (No votes)

See more:

Dear readers,

Seem to have a little problem with threading.

I setup a socket connection which a new AsyncCallback(OnDataReceived);

From now my Main Thread is unavaible:
Let's just call it System.Threading.Thread.Sleep(System.Threading.Timeout.Infinite);

When the OnDataReceived is called it has to create a new class instance,
But events inside this class won't fire.

I believe it's because that the main thread is unavailible and the OndataReceived Worker Thread ends,
So i tried putting the class instancing into a Thread: new Thread(new ThreadStart(startclass));

But after running the constructor the thread ends and the events never get called.
How do i keep this thread alive and so that it can handle events?

Thanks

Posted 15-May-11 13:50pm

Scalee

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2011-05-15T15:06:00

Wow! Isn't that obvious that you try to defeat the purpose of nearly everything you try here?

Using System.Threading.Thread.Sleep(System.Threading.Timeout.Infinite) is the same as not using the thread at all. There is not situation when such kind of sleep is useful. You artificially create unavailable thread and as a work-around you create yet another thread! What an abuse!

First of all, once you use threads (and yes, you should better do all networking in separate threads), why using asynchronous sockets at all? Instead, use threads and use blocking calls. When the thread is using blocking call, it's also "sleeping", but sleeping in a "productive manner", it enters the wait state when it is switched off by the system and is not scheduled back to execution (so it waste zero CPU time) until it is waken up. What wakes it up include: completion of blocking method call, timeout, Thread.Interrupt or Thread.Abort.

Perhaps you need to rethink the whole design. I don't know what you want to achieve, but please look at some my past answers to get an idea on working variants of design:
Multple clients from same port Number[^].
This is my collection of links to some my past answers on threading:
How to get a keydown event to operate on a different thread in vb.net[^],
Control events not firing after enable disable + multithreading[^].

—SA

rwg · Answer 2 · 2011-05-15T15:01:00

Solution 1

If you instantiate a new thread, I believe you will have to register new event handlers.

Posted 15-May-11 15:01pm

rwg

parmar_punit · Answer 3 · 2011-05-15T20:19:00

There is AutoResetEvent class in .net framework...
Use two methods of this class named WaitOne() and Set();

MIDL

//declare this object on the constructor of that class...
AutoResetEvent obj = new AutoResetEvent(false);

// call the WaitOne() method after calling any asynchronous method or Thread...
obj.WaitOne();


// call the Set() method in as the last statement of asynchronous method or Thread that you have called before
obj.Set();

Thread and Event problem

3 solutions

Solution 2

Solution 1

Solution 3

Add your solution here

Preview 0