Re^2: How to pass a object value to global array in threads

Yes I am trying to do wrong thing. but I am not able to get is in the explanation that 4rth thread will return the information to calling thread. but again i will be having same problem using that handle. See my problem is because of legacy code. I required to store all the telnet handle to an global array and that array of handles is used every where. so with your solution i will also have same problem.

May be my question how to get all telnet start at a same time and get it handle stored in a array for further use. Is there is any better way to do it?

Comment on Re^2: How to pass a object value to global array in threads

Replies are listed 'Best First'.
Re^3: How to pass a object value to global array in threads by BrowserUk (Patriarch) on Oct 26, 2015 at 10:08 UTC
See my problem is because of legacy code. I required to store all the telnet handle to an global array and that array of handles is used every where. That simply makes no sense. If modern code (of any type or language) cannot successfully make concurrent use of a shared telnet session; neither can legacy code. And if you cannot use the telnet handle concurrently, there is no reason and it makes no sense, to store them in a shared global array. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". I knew I was on the right track :) In the absence of evidence, opinion is indistinguishable from prejudice.	[reply]

Replies are listed 'Best First'.

Re^3: How to pass a object value to global array in threads
by BrowserUk (Patriarch) on Oct 26, 2015 at 10:08 UTC

See my problem is because of legacy code. I required to store all the telnet handle to an global array and that array of handles is used every where.

That simply makes no sense. If modern code (of any type or language) cannot successfully make concurrent use of a shared telnet session; neither can legacy code.

And if you cannot use the telnet handle concurrently, there is no reason and it makes no sense, to store them in a shared global array.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority". I knew I was on the right track :)

In the absence of evidence, opinion is indistinguishable from prejudice.

[reply]