Aggiustata Chiusura #1
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… importa di chiudere e lo lasciamo fare alla jvm
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Aggiunta coda per gestire l'input utente, praticamente abbiamo spostato il problema dal sender del client ad un nuovo thread che ho chiamato t, giusto per provare.
Cosa succede adesso:
-Utente scrive messaggio in cli
-Thread t vede il messaggio essendo bloccato su scanner.nextline()
-Thread t mette sulla coda userCli il messaggio
-Thread ClientSender è bloccato sulla take della coda e riceve l'input dell'utente
Questo serve per fare in modo che quando il server si chiude noi possiamo mandare un messaggio SHUTDOWN_WARNING sulla coda, tale messaggio verrà letto dal ClientSender che potrà così chiudere.
il thread t è un demone e quindi ci pensa la jvm a sterminarlo