|
Well, yes, it is a Threading issue - but......
This could be done in a Thread: public void connecting() throws IOException { and single threading is what is blocking the app, yes - but implementing reasonably relaible threading even as a student level work is remarkably fraught with frustrations and hidden errors that do not detect even with sophisticated techniques paired with deep consideration of the Threading domain.
Do you need help getting threads to talk across the application? Getting some get-going techinques for intra-process communication is neither difficult nor advanced, it is shielding ones efforts from failure in commercial grade applications that proves wisdom to be 'leave it alone'. Inter-process communication is another matter.
Just start with a static synchornized accessor( Object getSet ) and do a little twiddling in a super-simplified one-off written for the purpose of learning. If you are getting paid to do the work, you are on your own. Google for Java Real Time Specification, read the whole tuna.
Read every word in it's entire current form.
|