OOP Lab Task 6 - Revizia istoricului

Zhascsi: /* Requirements */

2016-12-22T13:12:56Z

Requirements

Zhascsi: /* Requirements */

2016-12-22T13:11:51Z

Requirements

Zhascsi: /* Requirements */

2016-12-22T13:09:01Z

Requirements

Zhascsi: /* Requirements */

2016-12-22T13:07:14Z

Requirements

Zhascsi: /* Requirements */

2016-12-22T12:54:28Z

Requirements

Zhascsi: /* Requirements */

2016-12-22T12:51:43Z

Requirements

Zhascsi: /* Requirements */

2016-12-22T12:50:36Z

Requirements

Zhascsi: /* Requirements */

2016-12-22T12:43:10Z

Requirements

Zhascsi: /* Requirements */

2016-12-22T12:40:51Z

Requirements

Zhascsi: /* Submitting */

2016-11-09T23:34:45Z

Submitting

@@ Linia 48: / Linia 48: @@
 #* Change the '''main''' method so that it instantiates a '''Socket''' connected to some peer host (try first with the local host, "127.0.0.1"), and then it instantiates a '''ClientFrame''' with that socket.
 #* Modify the class '''Server''' so that its '''run''' method, instead of instantiating and running a '''ServerPeer''' (which no longer exists in this project), instantiates a '''ClientFrame''' object. The '''ClientFrame''''s constructor arguments are a string (the name of the client on the server side) and a socket returned by the '''accept''' method called for the '''ServerSocket''' object.
-#* You are now ready to open a connection. Run first the Server file, then run the Client file. After the connection is established you will see two client GUIs on the screen. For the moment they do not communicate.
+#* You are now ready to open a connection. Run first the Server file, then run the ClientFrame file. After the connection is established you will see two client GUIs on the screen. For the moment they do not communicate.
 # To be able to send messages we need to do the text field responsive to the ''Enter'' key, so that when it is pressed, the text typed in this field is packaged as a message and sent over the connection. The packaging and send operation are already designed in the '''ClientPeer''' class, so you need only to couple the user operation on the GUI (pressing the ''Enter'' key) with the ''sendMessage'' method of the '''ClientPeer''' object.
 #* In the constructor, call the <code style="color:green;">addActionListener</code> method for the '''JTextField''' object. This method has a single argument, a reference to an object of type '''ActionListener''', the object that actually does the necessary coupling. But you need a type derived from that class, specifically designed for this task, to call a method of the '''ClientPeer''' a.s.o. Instead of designing a new file for this class, you will define that class right at its instantiation! You need it only here, so it doesn't need a name. This is an ''anonymous class''. An anonymous class declared inside a method of some other class has the big advantage that it has access to all fields of the later class. Your anonymous class will have acces to '''ClientFrame''''s name, and to references to the '''ClientPeer''' and the graphical objects. The body of this anonymous class has only one method, the overridden <code style="color:green;">public void actionPerformed(ActionEvent e)</code> method of the '''ActionListener'''. This method is called automatically when the user presses the ''Enter'' key inside the graphical component to which this listener is attached (and you attach it to the text field). In this method you need to do the following:

@@ Linia 47: / Linia 47: @@
 #* The '''ClientFrame''' object encapsulates a '''ClientPeer''' object which manages the communication between clients. Instantiate a '''ClientPeer''' in the constructor. Its instantiation needs two arguments, the name and a reference to a '''Socket''' object. Change the '''ClientFrame''' constructor declaration so that it accepts two arguments, the name and a reference to a '''Socket'''. These two arguments are passed to the '''ClientPeer''' instantiation. The reference to '''ClientPeer''' needs to be an instance field too, in order to allow the ClientPeer to interact with the GUI.
 #* Change the '''main''' method so that it instantiates a '''Socket''' connected to some peer host (try first with the local host, "127.0.0.1"), and then it instantiates a '''ClientFrame''' with that socket.
-#* Modify the class '''Server''' so that its '''main''' method, instead of instantiating and running a '''ServerPeer''' (which no longer exists in this project), instantiates a '''ClientFrame''' object. The '''ClientFrame''''s constructor arguments are a string (the name of the client on the server side) and a socket returned by the '''accept''' method called for the '''ServerSocket''' object.
+#* Modify the class '''Server''' so that its '''run''' method, instead of instantiating and running a '''ServerPeer''' (which no longer exists in this project), instantiates a '''ClientFrame''' object. The '''ClientFrame''''s constructor arguments are a string (the name of the client on the server side) and a socket returned by the '''accept''' method called for the '''ServerSocket''' object.
 #* You are now ready to open a connection. Run first the Server file, then run the Client file. After the connection is established you will see two client GUIs on the screen. For the moment they do not communicate.
 # To be able to send messages we need to do the text field responsive to the ''Enter'' key, so that when it is pressed, the text typed in this field is packaged as a message and sent over the connection. The packaging and send operation are already designed in the '''ClientPeer''' class, so you need only to couple the user operation on the GUI (pressing the ''Enter'' key) with the ''sendMessage'' method of the '''ClientPeer''' object.

@@ Linia 46: / Linia 46: @@
 # It's time to add functionality to the GUI. It will be defined also in the constructor, in its second part:
 #* The '''ClientFrame''' object encapsulates a '''ClientPeer''' object which manages the communication between clients. Instantiate a '''ClientPeer''' in the constructor. Its instantiation needs two arguments, the name and a reference to a '''Socket''' object. Change the '''ClientFrame''' constructor declaration so that it accepts two arguments, the name and a reference to a '''Socket'''. These two arguments are passed to the '''ClientPeer''' instantiation. The reference to '''ClientPeer''' needs to be an instance field too, in order to allow the ClientPeer to interact with the GUI.
-#* Change the '''main''' method so that it instantiates a '''Socket''' connected to some peer host (try first with the local host, "127.0.0.1"), and then it instantiates a '''Client''' with that socket.
+#* Change the '''main''' method so that it instantiates a '''Socket''' connected to some peer host (try first with the local host, "127.0.0.1"), and then it instantiates a '''ClientFrame''' with that socket.
 #* Modify the class '''Server''' so that its '''main''' method, instead of instantiating and running a '''ServerPeer''' (which no longer exists in this project), instantiates a '''ClientFrame''' object. The '''ClientFrame''''s constructor arguments are a string (the name of the client on the server side) and a socket returned by the '''accept''' method called for the '''ServerSocket''' object.
 #* You are now ready to open a connection. Run first the Server file, then run the Client file. After the connection is established you will see two client GUIs on the screen. For the moment they do not communicate.

@@ Linia 45: / Linia 45: @@
 #* call somewhere in the constructor the parent method <code style="color:green;">setDefaultCloseOperation</code> whose argument tells the object what to do if the frame window is closed. We want the client application to end (so that it not remains active after the GUI interface dissapears, wasting computer resourses and needing the OS intervention to be killed). The argument value that defines this behavior is the constant value <code style="color:green;">EXIT_ON_CLOSE</code> inherited from the parent class.
 # It's time to add functionality to the GUI. It will be defined also in the constructor, in its second part:
-#* The '''ClientFrame''' object encapsulates a '''ClientPeer''' object which manages the communication between clients. Instantiate a '''ClientPeer''' in the constructor. Its instantiation needs two arguments, the name and a reference to a '''Socket''' object. Change the '''Client''' constructor declaration so that it accepts two arguments, the name and a reference to a '''Socket'''. These two arguments are passed to the '''ClientPeer''' instantiation. The reference to '''ClientPeer''' needs to be an instance field too, in order to allow the ClientPeer to interact with the GUI.
+#* The '''ClientFrame''' object encapsulates a '''ClientPeer''' object which manages the communication between clients. Instantiate a '''ClientPeer''' in the constructor. Its instantiation needs two arguments, the name and a reference to a '''Socket''' object. Change the '''ClientFrame''' constructor declaration so that it accepts two arguments, the name and a reference to a '''Socket'''. These two arguments are passed to the '''ClientPeer''' instantiation. The reference to '''ClientPeer''' needs to be an instance field too, in order to allow the ClientPeer to interact with the GUI.
 #* Change the '''main''' method so that it instantiates a '''Socket''' connected to some peer host (try first with the local host, "127.0.0.1"), and then it instantiates a '''Client''' with that socket.
 #* Modify the class '''Server''' so that its '''main''' method, instead of instantiating and running a '''ServerPeer''' (which no longer exists in this project), instantiates a '''ClientFrame''' object. The '''ClientFrame''''s constructor arguments are a string (the name of the client on the server side) and a socket returned by the '''accept''' method called for the '''ServerSocket''' object.

@@ Linia 45: / Linia 45: @@
 #* call somewhere in the constructor the parent method <code style="color:green;">setDefaultCloseOperation</code> whose argument tells the object what to do if the frame window is closed. We want the client application to end (so that it not remains active after the GUI interface dissapears, wasting computer resourses and needing the OS intervention to be killed). The argument value that defines this behavior is the constant value <code style="color:green;">EXIT_ON_CLOSE</code> inherited from the parent class.
 # It's time to add functionality to the GUI. It will be defined also in the constructor, in its second part:
-#* The '''Client''' object encapsulates a '''ClientPeer''' object which manages the communication between clients. Instantiate a '''ClientPeer''' in the constructor. Its instantiation needs two arguments, the name and a reference to a '''Socket''' object. Change the '''Client''' constructor declaration so that it accepts two arguments, the name and a reference to a '''Socket'''. These two arguments are passed to the '''ClientPeer''' instantiation. The reference to '''ClientPeer''' needs to be an instance field too, in order to allow the ClientPeer to interact with the GUI.
+#* The '''ClientFrame''' object encapsulates a '''ClientPeer''' object which manages the communication between clients. Instantiate a '''ClientPeer''' in the constructor. Its instantiation needs two arguments, the name and a reference to a '''Socket''' object. Change the '''Client''' constructor declaration so that it accepts two arguments, the name and a reference to a '''Socket'''. These two arguments are passed to the '''ClientPeer''' instantiation. The reference to '''ClientPeer''' needs to be an instance field too, in order to allow the ClientPeer to interact with the GUI.
 #* Change the '''main''' method so that it instantiates a '''Socket''' connected to some peer host (try first with the local host, "127.0.0.1"), and then it instantiates a '''Client''' with that socket.
 #* Modify the class '''Server''' so that its '''main''' method, instead of instantiating and running a '''ServerPeer''' (which no longer exists in this project), instantiates a '''ClientFrame''' object. The '''ClientFrame''''s constructor arguments are a string (the name of the client on the server side) and a socket returned by the '''accept''' method called for the '''ServerSocket''' object.
 #* You are now ready to open a connection. Run first the Server file, then run the Client file. After the connection is established you will see two client GUIs on the screen. For the moment they do not communicate.
 # To be able to send messages we need to do the text field responsive to the ''Enter'' key, so that when it is pressed, the text typed in this field is packaged as a message and sent over the connection. The packaging and send operation are already designed in the '''ClientPeer''' class, so you need only to couple the user operation on the GUI (pressing the ''Enter'' key) with the ''sendMessage'' method of the '''ClientPeer''' object.
-#* In the constructor, call the <code style="color:green;">addActionListener</code> method for the '''JTextField''' object. This method has a single argument, a reference to an object of type '''ActionListener''', the object that actually does the necessary coupling. But you need a type derived from that class, specifically designed for this task, to call a method of the '''ClientPeer''' a.s.o. Instead of designing a new file for this class, you will define that class right at its instantiation! You need it only here, so it doesn't need a name. This is an ''anonymous class''. An anonymous class declared inside a method of some other class has the big advantage that it has access to all fields of the later class. Your anonymous class will have acces to '''Client''' name, and to references to the '''ClientPeer''' and the graphical objects. The body of this anonymous class has only one method, the overridden <code style="color:green;">public void actionPerformed(ActionEvent e)</code> method of the '''ActionListener'''. This method is called automatically when the user presses the ''Enter'' key inside the graphical component to which this listener is attached (and you attach it to the text field). In this method you need to do the following:
+#* In the constructor, call the <code style="color:green;">addActionListener</code> method for the '''JTextField''' object. This method has a single argument, a reference to an object of type '''ActionListener''', the object that actually does the necessary coupling. But you need a type derived from that class, specifically designed for this task, to call a method of the '''ClientPeer''' a.s.o. Instead of designing a new file for this class, you will define that class right at its instantiation! You need it only here, so it doesn't need a name. This is an ''anonymous class''. An anonymous class declared inside a method of some other class has the big advantage that it has access to all fields of the later class. Your anonymous class will have acces to '''ClientFrame''''s name, and to references to the '''ClientPeer''' and the graphical objects. The body of this anonymous class has only one method, the overridden <code style="color:green;">public void actionPerformed(ActionEvent e)</code> method of the '''ActionListener'''. This method is called automatically when the user presses the ''Enter'' key inside the graphical component to which this listener is attached (and you attach it to the text field). In this method you need to do the following:
 #** call the <code style="color:green;">getText</code> for the '''JTextField''' object to read the typed string;
 #** call the <code style="color:green;">sendMessage</code> for the '''ClientPeer''', passing to it your name and the typed string;
@@ Linia 58: / Linia 58: @@
 #* Some classes used here are part of '''java.awt.event''' package.
 # To display messages in real time a separate thread is needed, so that the main thread that sends messages is not blocked by message reading when this last operation waits for a message to be received.
-#* Make the '''Client''' class '''Runnable'''.
+#* Make the '''ClientFrame''' class '''Runnable'''.
 #* Override the '''run''' method of the '''Runnable''' interface. This method will loop forever (or until the connection is closed by the peer). In each iteration it:
 #** calls the <code style="color:green;">readMessage</code> for the '''ClientPeer''' object to get the formatted version of the received message. This method waits until a message is received from the connection.
 #** calls the <code style="color:green;">append</code> method for the '''JTextArea''' object to append the received message, together with a newline at its end.
 #** Because '''readMessage''' may throw an exception, enclose it in a '''try'''-'''catch''' block and catch the exception to break the loop.
-#* In the '''Client''' constructor instantiate a '''Thread''' object with the curent '''Client''' object as the argument (use the '''this''' reference). For this '''Thread''' object call the <code style="color:green;">start</code> method, that actually initiates the new thread which will execute the '''run''' method of this '''Client''' object.
+#* In the '''ClientFrame''''s constructor instantiate a '''Thread''' object with the curent '''ClientFrame''' object as the argument (use the '''this''' reference). For this '''Thread''' object call the <code style="color:green;">start</code> method, that actually initiates the new thread which will execute the '''run''' method of this '''ClientFrame''' object.
-# Everything is in place! Run the Server file, then run the Client file. You are able now to communicate between twese to client GUIs.
+# Everything is in place! Run the Server file, then run the ClientFrame file. You are able now to communicate between twese to client GUIs.
-# For more fun, run a server and ask a colleague to run a client on his computer, with the host address (set upon '''Client''' instantiation in the '''main''' method) equal to your IP address.
+# For more fun, run a server and ask a colleague to run a client on his computer, with the host address (set upon '''ClientFrame''' instantiation in the '''main''' method) equal to your IP address.
 Note: If you want to declare an anonymous class derived from some class, named ''BaseClass'', and to override the method ''baseMethod'', use the following structure:
@@ Linia 77: / Linia 77: @@
 </syntaxhighlight>
-To stop correctly the Client some additional steps are needed at the end of the '''Client''' constructor. A call to <code style="color:green;">join</code> for the thread object will synchronize the constructor with the started thread. The constructor will wait for the thread to finish, and the thread finishes when the connection is closed or something exceptional happens. After that, you call the <code style="color:green;">close</code> method of the '''ClientPeer''' object to close the streams. At the very end close the socket.
+To stop correctly the ClientFrame some additional steps are needed at the end of the '''ClientFrame''' constructor. A call to <code style="color:green;">join</code> for the thread object will synchronize the constructor with the started thread. The constructor will wait for the thread to finish, and the thread finishes when the connection is closed or something exceptional happens. After that, you call the <code style="color:green;">close</code> method of the '''ClientPeer''' object to close the streams. At the very end close the socket.
 == Submitting ==

@@ Linia 37: / Linia 37: @@
 #* If you do not want the frame size to be explicitly defined, but you want it to adapt to the specified dimensions of the text area and text field, call the method <code style="color:green;">pack</code>, inherited from the parent '''JFrame''' class.
 #* In order to display the frame, call the parent class method <code style="color:green;">setVisible</code> with the proper argument value.
-#* Your frame is ready to be displayed. You need only to explicitly instantiate a '''Client''' object.
+#* Your frame is ready to be displayed. You need only to explicitly instantiate a '''ClientFrame''' object.
 # Add to '''ClientFrame''' class the '''main''' method, and put a single statement inside, the instantiation of a '''ClientFrame''' object. Run the class and you will see a window like the one shown above.
 # Cosmeticize the GUI class as follows:
@@ Linia 47: / Linia 47: @@
 #* The '''Client''' object encapsulates a '''ClientPeer''' object which manages the communication between clients. Instantiate a '''ClientPeer''' in the constructor. Its instantiation needs two arguments, the name and a reference to a '''Socket''' object. Change the '''Client''' constructor declaration so that it accepts two arguments, the name and a reference to a '''Socket'''. These two arguments are passed to the '''ClientPeer''' instantiation. The reference to '''ClientPeer''' needs to be an instance field too, in order to allow the ClientPeer to interact with the GUI.
 #* Change the '''main''' method so that it instantiates a '''Socket''' connected to some peer host (try first with the local host, "127.0.0.1"), and then it instantiates a '''Client''' with that socket.
-#* Modify the class '''Server''' so that its '''main''' method, instead of instantiating and running a '''ServerPeer''' (which no longer exists in this project), instantiates a '''Client''' object. The '''Client''' arguments are a string (the name of the client on the server side) and a socket returned by the '''accept''' method called for the '''ServerSocket''' object.
+#* Modify the class '''Server''' so that its '''main''' method, instead of instantiating and running a '''ServerPeer''' (which no longer exists in this project), instantiates a '''ClientFrame''' object. The '''ClientFrame''''s constructor arguments are a string (the name of the client on the server side) and a socket returned by the '''accept''' method called for the '''ServerSocket''' object.
 #* You are now ready to open a connection. Run first the Server file, then run the Client file. After the connection is established you will see two client GUIs on the screen. For the moment they do not communicate.
 # To be able to send messages we need to do the text field responsive to the ''Enter'' key, so that when it is pressed, the text typed in this field is packaged as a message and sent over the connection. The packaging and send operation are already designed in the '''ClientPeer''' class, so you need only to couple the user operation on the GUI (pressing the ''Enter'' key) with the ''sendMessage'' method of the '''ClientPeer''' object.

@@ Linia 25: / Linia 25: @@
 #** The '''close''' method needs now to close both streams, the input stream and the output stream.
 #* Remember! All fields are private, all methods are public.
-# The client will be enclosed in a graphical user interface (GUI) frame, with two areas, one for typing the messages to be sent, and another area that displays in real time all messages. A message is sent the moment you press the ''Enter'' key. Also, when ''Enter'' is pressed the write area is emptied and your message is shown as the last message in the display area. All messages, sent and received, are displayed as formatted strings ''name'':''message''. Add to your package a class named <code style="color:green;">Client</code>, that will manage the GUI frame and the ClientPeer. You may reuse the '''Client''' class from the previous package, but it needs to be thorougly modified, so it's better to create it from scratch. This class will be designed in two steps. First, you design the GUI frame. Then you will add the functionality, coupling the GUI frame to the ClientPeer object. The GUI frame to design is the following:
+# The client will be enclosed in a graphical user interface (GUI) frame, with two areas, one for typing the messages to be sent, and another area that displays in real time all messages. A message is sent the moment you press the ''Enter'' key. Also, when ''Enter'' is pressed the write area is emptied and your message is shown as the last message in the display area. All messages, sent and received, are displayed as formatted strings ''name'':''message''. Add to your '''labutil''' package a class named <code style="color:green;">ClientFrame</code>, that will manage the GUI frame and the ClientPeer. This class will be designed in two steps. First, you design the GUI frame. Then you will add the functionality, coupling the GUI frame to the ClientPeer object. The GUI frame to design is the following:
 #[[Fişier:lab6_client.png]]
-# The '''Client''' class extends the '''JFrame''' class from the '''javax.swing''' package. An object of JFrame type is a GUI frame, to be open as a separate window on your screen. The frame itself, with its three upper right buttons, is drawn automatically by the JFrame object on the screen upon JFrame instantiation. You need to design only the content of the framed window (the so called ''content pane''), and all this may be done inside the constructor of the '''Client''' class, so that the frame is fully drawn upon its instantiation.
+# The '''ClientFrame''' class extends the '''JFrame''' class from the '''javax.swing''' package. An object of JFrame type is a GUI frame, to be open as a separate window on your screen. The frame itself, with its three upper right buttons, is drawn automatically by the JFrame object on the screen upon JFrame instantiation. You need to design only the content of the framed window (the so called ''content pane''), and all this may be done inside the constructor of the '''ClientFrame''' class, so that the frame is fully drawn upon its instantiation.
-#* The content pane for the Client has two parts, the display area and the typing area. These areas will be handled by two objects, that you instantiate as follows:
+#* The content pane for the ClientFrame has two parts, the display area and the typing area. These areas will be handled by two objects, that you instantiate as follows:
 #** a <code style="color:green;">JTextArea</code> object, instantiated with two arguments, the number of lines and the length of a line in number of characters. Instantiate the display area to have 10 lines with 40 characters per line.
 #** a <code style="color:green;">JTextField</code> object, instantiated with one argument, the length of the line in number of characters;
@@ Linia 38: / Linia 38: @@
 #* In order to display the frame, call the parent class method <code style="color:green;">setVisible</code> with the proper argument value.
 #* Your frame is ready to be displayed. You need only to explicitly instantiate a '''Client''' object.
-# Add to '''Client''' class the '''main''' method, and put a single statement inside, the instantiation of a '''Client''' object. Run the class and you will see a window like the one shown above.
+# Add to '''ClientFrame''' class the '''main''' method, and put a single statement inside, the instantiation of a '''ClientFrame''' object. Run the class and you will see a window like the one shown above.
 # Cosmeticize the GUI class as follows:
 #* declare the '''JtextArea''' and '''JTextField''' references as instance fields, so that they are accesible outside the constructor in this class. You will need them to couple the ClientPeer to user interface.

@@ Linia 16: / Linia 16: @@
 == Requirements ==
-−
-# Create a new project, named '''oop_lab6''' and use the same package '''labutil'''.
+# For this task you need the previously designed classes '''Message''', '''ClientPeer''' and '''Server'''. They are inside the package '''labutil'''.
 # The class '''ClientPeer''', which was used in the previous laboratory only to send messages, will manage a bidirectional connection, to send AND receive messages through it.
 #* Beside the '''ObjectOutputStream''' you need an input stream to read '''Message''' objects from. The following things need to be added to this class:

@@ Linia 83: / Linia 83: @@
 * The assignment will be evaluated automatically by the [http://homework.dcae.pub.ro:/WebObjects/Web-CAT.woa Web-CAT] platform.
 * You could access the Web-CAT platform using the username and the password with which you acces the <span style="color:red">electronica.curs.pub.ro</span> intranet.
-* Select the OOP Laboratory 6 assignment.
+* Select the OOP Lab Task 6 assignment.
 * Submit your work as a single .zip archive (give it whatever name you choose) containing only the Java source code files.
 * <font color="red">'''Attention'''</font> Any deviation from these instructions may lead to the loss of the entire amount of points.