Currently making a client/server application.
i create a server thread from the main GUI and then pass the gui object to the server thread.
Server thread is waiting for incoming connections . on a new connection it starts the connection handling in a new thread as application is multithreaded
Gui object from server thread is passed onto each of these new threads which can then update the main gui.
i know this is a bad way of doing it.
Any help to guide me in the right direction and suggestion would be much appreciated.
Dave cbank wrote:
Currently making a client/server application.
i create a server thread from the main GUI and then pass the gui object to the server thread.
Server thread is waiting for incoming connections . on a new connection it starts the connection handling in a new thread as application is multithreaded
Gui object from server thread is passed onto each of these new threads which can then update the main gui.
If by GUI, you mean Swing, remember that it is *not* thread safe. You have to make sure that all changes are done by the event dispatch thread.
0
