nikunj91 Goto Github PK

calculator-unit-test-example-java

Simple jUnit test example

course

expertiza

Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

fake-sandbox

game-of-life

Demo application for the 'Jenkins: The Definitive Guide' book

hw0

kaggle-stackoverflow

Predicting closed questions on Stack Overflow

library

librarymanagementsystem

Web application build over ruby on rails implementing a library management system

p2p-ci-system-for-downloading-rfcs

Peer-to-Peer with Centralized Index (P2P-CI) System for Downloading RFCs Internet protocol standards are defined in documents called “Requests for Comments” (RFCs). RFCs are available for download from the IETF web site (http://www.ietf.org/). Rather than using this centralized server for downloading RFCs, you will build a P2P-CI system in which peers who wish to download an RFC that they do not have in their hard drive, may download it from another active peer who does. All communication among peers or between a peer and the server will take place over TCP. Specifically, the P2P-CI system will operate as follows; additional details on each component of the system will be provided shortly. • There is a centralized server, running on a well-known host and listening on a well-known port, which keeps information about the active peers and maintains an index of the RFCs available at each active peer. • When a peer decides to join the P2P-CI system, it opens a connection to the server to register itself and provide information about the RFCs that it makes available to other peers. This connection remains open as long as the peer remains active; the peer closes the connection when it leaves the system (becomes inactive). • Since the server may have connections open to multiple peers simultaneously, it spawns a new process to handle the communication to each new peer. • When a peer wishes to download a specific RFC, it provides the RFC number to the server over the open connection, and in response the server provides the peer with a list of other peers who have the RFC; if no such active peer exists, an appropriate message is transmitted to the requesting peer. Additionally, each peer may at any point query the server to obtain the whole index of RFCs available at all other active peers. • Each peer runs a upload server process that listens on a port specific to the peer ; in other words, this port is not known in advance to any of the peers. When a peer A needs to download an RFC from a peer B, it opens a connection to the upload port of peer B, provides the RFC number to B, and B responds by sending the (text) file containing

selectiverepeatarq

simple-file-transfer-protocol-using-go-back-n-automatic-repeat-request-arq-scheme

Implemented the Go-back-N automatic repeat request (ARQ) scheme and carry out a number of experiments to evaluate its performance. In the process I expect that you will develop a good understanding of ARQ schemes and reliable data transfer protocols and build a number of fundamental skills related to writing transport layer services, including: • encapsulating application data into transport layer segments by including transport headers, • buffering and managing data received from, or to be delivered to, the application, • managing the window size at the sender, • computing checksums, and • using the UDP socket interface.

simplesetswebapp

start-here

You should open this repo first