Merge origin/master

deliverables/src/MV3500Cohort2018JulySeptember/homework1/FurrAssignment1.java

+package  MV3500Cohort2018JulySeptember.homework1;
+
+import java.io.*;
+import java.net.*;
+
+/**
+ * The simplest possible TCP network program. It listens for
+ * a connection, from telnet (telnet localhost 2317) or a program
+ * you write, which we will do later. Right now the TcpExample simply
+ * writes a string in response to a connection. 
+ * 
+ * Testing the running server program from telnet looks like this:
+ * 
+ * it154916:projects mcgredo$ telnet localhost 2317
+ * Trying ::1...
+ * Connected to localhost.
+ * Escape character is '^]'.
+ * This was written by the server
+ * Connection closed by foreign host.
+ * 
+ * Notice that "This was written by the server" matches 
+ * what is written by the code below, over the output stream.
+ * 
+ * After this first connection the program below drops out
+ * the bottom of the program, and does not repeat itself.
+ * The program exits.
+ * 
+ * @author mcgredo
+ */
+public class FurrAssignment1 
+{
+
+    public static void main(String[] args) 
+    {
+        try
+        {
+            // The ServerSocket waits for a connection from a client.
+            // It returns a Socket object when the connection occurs.
+            ServerSocket serverSocket = new ServerSocket(2317);
+            
+            // The Socket object represents the connection between
+            // the server and client, including a full duplex
+            // connection
+            Socket clientConnection = serverSocket.accept();
+            
+            // Use Java io classes to write text (as opposed to
+            // unknown bytes of some sort) to the client
+            OutputStream os = clientConnection.getOutputStream();
+            PrintStream ps = new PrintStream(os);
+            
+                    ps.println("This client response was written by server FurrAssignment1"); // to remote client
+            System.out.println("This server response was written by server FurrAssignment1"); // to server console
+			ps.println("Thanks for showing up it's been fun, but you have to go now.  Goodbye!");  //added a goodbye message, it really has been fun!
+            
+            // "flush()" in important in that it forces a write 
+            // across what is in fact a slow connection
+            ps.flush();
+            
+            clientConnection.close();
+        }
+        catch(Exception e)
+        {
+            System.out.println("problem with networking: " + e);
+        }
+    }
+}

deliverables/src/MV3500Cohort2018JulySeptember/homework1/FurrAssignment2.java

+
 package MV3500Cohort2018JulySeptember.homework1;
 
 import java.io.*;

projects/Assignments/2018JulySeptember/homework1/FurrAssignment2.java

-
-package FurrAssignment2;
-
-import java.io.*;
-import java.net.*;
-
-/**
- * Very slightly more complex than example1. The only thing this does
- * differently is introduce a loop into the response, so you don't
- * have to restart the program after one response. Also, it prints
- * out the socket pair the server sees. Run the program via telnet
- * several times and compare the socket pairs.
- * 
- * telnet localhost 2317
- * 
- * If you're sophisticated you can contact the instructor's computer
- * while running this program.
- * 
- * telnet <ipOfServersLaptop> 2317
- * 
- * And have him display the socket pairs he got.
- * @author mcgredo
- */
-public class FurrAssignment2 
-{
-
-    public static void main(String[] args) 
-    {
-        try
-        {
-            // ServerSocket waits for a connection from a client. 
-            // Notice that it is outside the loop; ServerSocket
-            // needs to be made only once.
-			
-			int connectionCount = 0; // state
-            for(int i=2317; i<10; i++){
-				ServerSocket serverSocket = new ServerSocket(i);
-				System.out.println("server established for port #" +i);
-			}
-
-            // Loop, infinitely, waiting for client connections.
-            // Stop the program somewhere else.
-            while(true)
-            {
-                Socket clientConnection = serverSocket.accept(); // blocks! then proceeds once a connection is "accept"ed
-				
-				connectionCount++; // got another one!
-				
-                OutputStream os = clientConnection.getOutputStream();
-                PrintStream ps = new PrintStream(os);
-
-				        ps.println("This client response was written by server TcpExample2"); // to remote client
-				System.out.println("This server response was written by server TcpExample2"); // to server console
-                
-                // Print some information locally about the Socket
-                // connection. This includes the port and IP numbers
-                // on both sides (the socket pair.)
-                
-                InetAddress localAddress = clientConnection.getLocalAddress();
-                InetAddress remoteAddress = clientConnection.getInetAddress();
-                
-                int localPort = clientConnection.getLocalPort();
-                int remotePort = clientConnection.getPort();
-                
-                // My socket pair connection looks like this, to localhost:
-                // Socket pair: (( /0:0:0:0:0:0:0:1, 2317 ), ( /0:0:0:0:0:0:0:1, 54876 ))
-                // Socket pair: (( /0:0:0:0:0:0:0:1, 2317 ), ( /0:0:0:0:0:0:0:1, 54881 ))
-                //
-                // Why is the first IP/port the same, while the second set has
-                // different ports?
-
-
-                System.out.println("Socket pair: (( " + localAddress.toString() + ", " + localPort + " ), ( " + 
-                        remoteAddress.toString() + ", " + remotePort + " ))");
-                
-                System.out.println("got another connection, #" + connectionCount); // report progress
-				
-                // Notice the use of flush() and close(). Without
-                // the close() to Socket object may stay open for 
-                // a while after the client has stopped needing this
-                // connection. Close() explicitly ends the connection.
-                ps.flush();
-                clientConnection.close();
-            }
-       }
-        catch(Exception e)
-        {
-            System.out.println("problem with networking: " + e);
-        }
-       
-    }
-    
-}

projects/Assignments/dist/README.TXT

+========================
+BUILD OUTPUT DESCRIPTION
+========================
+
+When you build an Java application project that has a main class, the IDE
+automatically copies all of the JAR
+files on the projects classpath to your projects dist/lib folder. The IDE
+also adds each of the JAR files to the Class-Path element in the application
+JAR files manifest file (MANIFEST.MF).
+
+To run the project from the command line, go to the dist folder and
+type the following:
+
+java -jar "Assignments__MV3500_Homework.jar" 
+
+To distribute this project, zip up the dist folder (including the lib folder)
+and distribute the ZIP file.
+
+Notes:
+
+* If two JAR files on the project classpath have the same name, only the first
+JAR file is copied to the lib folder.
+* Only JAR files are copied to the lib folder.
+If the classpath contains other types of files or folders, these files (folders)
+are not copied.
+* If a library on the projects classpath also has a Class-Path element
+specified in the manifest,the content of the Class-Path element has to be on
+the projects runtime path.
+* To set a main class in a standard Java project, right-click the project node
+in the Projects window and choose Properties. Then click Run and enter the
+class name in the Main Class field. Alternatively, you can manually type the
+class name in the manifest Main-Class element.