corrections in Readme.md
This commit is contained in:
		
							parent
							
								
									e460487550
								
							
						
					
					
						commit
						fc6a91d3a8
					
				| 
						 | 
					@ -31,7 +31,7 @@ We decided to realise the second solution, because if a Client could have multip
 | 
				
			||||||
 | 
					
 | 
				
			||||||
###4. Direct Messages not possible when username has special characters(Issue [#19](https://github.zhaw.ch/PM2-IT21bWIN-ruiz-mach-krea/Uebung-hk1-Schrom01-Fassband-Brandleo/issues/19))
 | 
					###4. Direct Messages not possible when username has special characters(Issue [#19](https://github.zhaw.ch/PM2-IT21bWIN-ruiz-mach-krea/Uebung-hk1-Schrom01-Fassband-Brandleo/issues/19))
 | 
				
			||||||
 | 
					
 | 
				
			||||||
###5. Message stays in input field after being sent [#8](https://github.zhaw.ch/PM2-IT21bWIN-ruiz-mach-krea/Uebung-hk1-Schrom01-Fassband-Brandleo/issues/8))
 | 
					###5. Message stays in input field after being sent (Issue [#8](https://github.zhaw.ch/PM2-IT21bWIN-ruiz-mach-krea/Uebung-hk1-Schrom01-Fassband-Brandleo/issues/8))
 | 
				
			||||||
If a User had sent a message, the Message wasn't removed from the message field.
 | 
					If a User had sent a message, the Message wasn't removed from the message field.
 | 
				
			||||||
We decided to remove the message only if the message was sent sucessfully. So if there is a typing mistake in the username of the receiver, the user can do a correction without having to rewrite the whole message.
 | 
					We decided to remove the message only if the message was sent sucessfully. So if there is a typing mistake in the username of the receiver, the user can do a correction without having to rewrite the whole message.
 | 
				
			||||||
The message field is cleared if the method message of the connection handler returns true.
 | 
					The message field is cleared if the method message of the connection handler returns true.
 | 
				
			||||||
| 
						 | 
					@ -67,7 +67,7 @@ The ChatWindowController adds listeners in the clientConnectionHandler and in Cl
 | 
				
			||||||
 | 
					
 | 
				
			||||||
### Structure of protocol:
 | 
					### Structure of protocol:
 | 
				
			||||||
####Datatype:
 | 
					####Datatype:
 | 
				
			||||||
A new Class Message represents a Message which can be sent from a Client to the Server from the Server to a Client and can also directly be stored in ClientMessageList. This makes it much easier to process the received data and to send a message because no String parsing and String building is needed. 
 | 
					A new Class Message represents a Message which can be sent from a Client to the Server and from the Server to a Client and can also directly be stored in ClientMessageList. This makes it much easier to process the received data and to send a message because no String parsing and String building is needed. 
 | 
				
			||||||
####Class ConnectionHandler
 | 
					####Class ConnectionHandler
 | 
				
			||||||
A new Abstract Class ConnectionHandler contains Code which is used in ClientConnectionHandler and ServerConnectionHandler. For Example Method send Data. This removes a lot of duplicated methods and data fields.
 | 
					A new Abstract Class ConnectionHandler contains Code which is used in ClientConnectionHandler and ServerConnectionHandler. For Example Method send Data. This removes a lot of duplicated methods and data fields.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
		Loading…
	
		Reference in New Issue