CS 542 Final Project Overview at Purdue University, Spring 2016
Dive into the CS 542 Final Project at Purdue University in Spring 2016. Learn about important deadlines, project submission details, and essential components for your project proposal. Explore topics like Java RMI concepts and processes, as well as useful links for implementing Java RMI and Linux socket API. Get insights on project ideas, implementation strategies, and platform considerations. Don't miss out on the chance to showcase your project through scheduled demonstrations after submission.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
CS 542 Final Project Overview Purdue University Spring 2016
Dont miss those dates The hard deadline for Project Proposal is Feb. 11, 2016. Last Date for Project Submission: April 14, 2016, 11:59 pm. Demonstration of projects will be scheduled on the next week after submission.
Project proposal Due to Feb 11 You can choose your own topic or one from the list. Must include: Project title Good idea to include: Description Implementation ideas and details Platform Programming Language Additional software Functionality Conditions and limitations
Java RMI useful links Overview Getting Started Using JavaTM RMI Example from the course web page
Java RMI Processes 1, 2, 3 run only once at the start and the rest of the time applications communicate with each other directly using only stub of remote object. Starting the application it is necessary to set option -Djava.rmi.server.codebase to the full path of the directory with binary files of the project.
Linux socket API useful links Beej's Guide to Network Programming Using Internet Sockets Programming Linux sockets, Part 1: Using TCP/IP Programming Linux sockets, Part 2: Using UDP More examples
Connection establishment Data (request) Data reply
