This preview has intentionally blurred sections. Sign up to view the full version.View Full Document
Unformatted text preview: COP5615 Distributed Operating Systems Fall 2011 Computer and Information Science and Engineering University of Florida Project 1 Date Assigned: Sep 8th 2011 Office: CSE E309 in office hours Due[Campus]: Sep 16th 2011 local 23:59 pm TA : Kun Li ([email protected]) Due[EDGE]: Sep 19th 2011 edge 23:59 pm In project 1 our main goal is to familiarize you with java socket programming. Resources: Sun Microsystems Guide to Sockets: http://download.oracle.com/javase/tutorial/networking/sockets/ Makefile Tutorial: http://web.mit.edu/gnu/doc/html/make_toc.html Grading Guidelines: Coding Style (comments, indentations) 10% Clean Termination (runaway processes) 10% Correct Implementation 70% Report and User Documentation 10% For the first three projects, the primary TA who is responsible for creating the project will perform grading. But regardless of who grades the project, the TAs will follow the general guidelines for grading given above. Late Submission Policy: Late submissions are not encouraged but we rather have you submit a working version than submit a version that is broken or worse not submit at all. Every late submission will be penalized 10% for each business day late for up to a maximum of 5 days from the due date. Guidelines for Project Report: In addition to submitting any relevant user documentation that will help a third person to compile your code and execute it, we require that you submit a one-page report. Your report file must be named report.txt. Since we will use a UNIX environment during grading phase, we recommend you use a UNIX friendly text editor (gedit, nano, pico, vi, etc.). Your report file should contain details on what you learned from this project, what challenges you faced, how you overcame those, and any other observation, improvements, or interesting facts you might want to pass on to the instructor and the TA. CISE Systems Help and Related Issues: The TA for this class is not responsible for managing CISE department’s computing facilities. So if you run into any access problems with your account or if you find some remote machine unresponsive while implementing your project, your best bet will be to contact the CISE admin people directly at [email protected] Do NOT email the Tas regarding such issues, the Tas already receive tons of emails. Help your Tas fight insanity ☺ First semester EDGE students may not have created a valid CISE account yet. They should contact the CISE administrators for account creation. Without a valid CISE account you cannot log on to CISE machines. http://www.cise.ufl.edu/help/ has all the necessary details on CISE clusters and remote machines. You might want to look into this page to figure out what machine to use and where to execute your codes. We require you to write your programs to run correctly in the CISE UNIX environment. WE WILL NOT TEST ON WINDOWS SYSTEMS .Use of IDEs and other Development Tools: We do not have any preference on what tool you use to write your code. However, keep in mind that we will be compiling and grading your code on a UNIX system through code....
View Full Document
This note was uploaded on 01/18/2012 for the course COP 5615 taught by Professor Staff during the Fall '08 term at University of Florida.
- Fall '08
- Operating Systems