<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel rdf:about="http://dspace.dtu.ac.in:8080/jspui/handle/123456789/48">
    <title>DSpace Collection:</title>
    <link>http://dspace.dtu.ac.in:8080/jspui/handle/123456789/48</link>
    <description />
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://dspace.dtu.ac.in:8080/jspui/handle/repository/13580" />
        <rdf:li rdf:resource="http://dspace.dtu.ac.in:8080/jspui/handle/repository/13525" />
        <rdf:li rdf:resource="http://dspace.dtu.ac.in:8080/jspui/handle/repository/13518" />
        <rdf:li rdf:resource="http://dspace.dtu.ac.in:8080/jspui/handle/repository/13363" />
      </rdf:Seq>
    </items>
    <dc:date>2026-04-28T04:02:15Z</dc:date>
  </channel>
  <item rdf:about="http://dspace.dtu.ac.in:8080/jspui/handle/repository/13580">
    <title>IMPLEMENTATION OF ECHO SERVER</title>
    <link>http://dspace.dtu.ac.in:8080/jspui/handle/repository/13580</link>
    <description>Title: IMPLEMENTATION OF ECHO SERVER
Authors: SINGH, MADAN; KUMAR, RAVI; MATHUR, SIDDHARTH SAHAI
Abstract: Echo Service is a well known service running at port 7 for testing &amp; debugging purposes. Our project was to develop an Echo Server. Echo server is a simple server which echoes sent by client back to it. Clients for these are also presented ,but with lesser focus. The application of the echo server suggests simplicity ,robustness &amp; efficiency as prime requirements. Due Simplicity of application in case of echo server is synonymous with performance(simplicity reduces overhead) because of the simple nature of the service &amp; the reasons namely testing for which it is used. Hence any extra overhead in the form of a complex algorithm or complex programming techniques like recursion, synchronization is avoided. Though for some special cases different approaches have been presented in brief. These are provided at the end in the section of suggestion for improvement. Four types of servers are there; we covered three(Connectionless-iterative ,Connection -oriented iterative ,connection oriented Concurrent(common) )while the fourth Connectionless concurrent is rare. Except the initial servers, rest was designed for robustness/efficiency or both. Each type fulfills different requirements to different degrees &amp; hence, for different versions is developed. Echo service is mostly exploited by Ackers/malicious clients &amp; hence, their vulnerabilities are discussed with possible solutions are provided for those within our scope. The first two servers developed by us are Connection oriented Concurrent TCP server(general Process based) &amp; Connectionless Iterative UDP server(generally UDP servers are iterative).The next Server was a robust multi-mode version of the Concurrent TCP server with input validation, error checks , redundancy, acceptable behavior at boundary conditions, etc).The fourth one is a single process concurrent server to minimize resources based on I/O multiplexing. Lastly, the best option for an echo server ;the threaded server was used to reduce process forking overhead. The platform chosen was UNIX(posix.1g)/Linux owing to the efficiency &amp; simplicity of these systems &amp; the C language was used.&#xD;
3</description>
    <dc:date>2006-01-30T00:00:00Z</dc:date>
  </item>
  <item rdf:about="http://dspace.dtu.ac.in:8080/jspui/handle/repository/13525">
    <title>DESIGN AND IMPLEMENTATION OF ECHO SERVER</title>
    <link>http://dspace.dtu.ac.in:8080/jspui/handle/repository/13525</link>
    <description>Title: DESIGN AND IMPLEMENTATION OF ECHO SERVER
Authors: GOEL, ANURAG; AGARWAL, MANHAR P; OHRI, SAURABH
Description: BE FINAL YEAR PROJECT</description>
    <dc:date>2006-01-31T00:00:00Z</dc:date>
  </item>
  <item rdf:about="http://dspace.dtu.ac.in:8080/jspui/handle/repository/13518">
    <title>IMPLEMENTATION OF FILE TRANSFER PROTOCOL IN CLIENT SERVER MODEL</title>
    <link>http://dspace.dtu.ac.in:8080/jspui/handle/repository/13518</link>
    <description>Title: IMPLEMENTATION OF FILE TRANSFER PROTOCOL IN CLIENT SERVER MODEL
Authors: SAXENA, NEELABH; GUPTA, NISHANT; MEHRA, PARAG
Abstract: The FTP is basic and common service to exchange files between computers,&#xD;
namely hosts, over TCP/IP networks e.g., private networks or Internet. The&#xD;
FTP supports file transmission and character code conversion when&#xD;
exchanging text or binary files. The use of FTP is effective in exchanging or&#xD;
distributing of large volume of data over private networks and/or the&#xD;
Internet. FTP uses TCP as a transport protocol to provide reliable end-to-end&#xD;
connections. As it is necessary to log into the remote host, the user must&#xD;
have a user name and a password to access files and directories. The user&#xD;
who initiates the connection assumes the client function, while the server&#xD;
function is provided by the remote host.&#xD;
The thesis starts with an introduction to the basic networking and the OSI&#xD;
model, giving background to to grasp the rest of the contents. Then next is&#xD;
the explanantion of the Client Server Model.Follwing this is a report on File&#xD;
Transfer Protocol. It explains the various functions that the File Transfer&#xD;
Protocol performs. FTP can be used to download the files from a server node&#xD;
to the client node or upload a file from a client node to the server node. FTP&#xD;
can also be used to change the current working directory of the server/client&#xD;
and also can delete files on the server station. After this there are details of&#xD;
socket programming. Socket programming has been used extentensively&#xD;
throughtout the project. The various functions that have been frequently used&#xD;
like socket ( ), bind ( ), accept ( ), send ( ) etc have been explained along&#xD;
with all the possible forms that these functions can take.&#xD;
Next is the implementation of such a File Transfer Protocol using the&#xD;
programming language C. The functions being implemented in the the code&#xD;
are open, quit, exit, username, password, download, upload, change&#xD;
directory, show present working directory, list the contents of the current&#xD;
working directory. The code can be run on a Linux platform.&#xD;
In the next section, File Transfer Protocol is implemented using JAVA. The&#xD;
functions being implemented are Connect, Disconnect, Download, Upload&#xD;
and Delete. This code is platform independent and thus can be run on a&#xD;
variety of platforms like Windows and Linux. This gives its users an added&#xD;
advantage of platform independence.&#xD;
6&#xD;
The C and Java implementations are followed by their respective possible&#xD;
outputs and errors. Also a brief comparison between the the codes is also&#xD;
done highlighting the major advantages and disadvantages of using C and JAVA.
Description: BE PROJECT REPORT</description>
    <dc:date>2006-01-30T00:00:00Z</dc:date>
  </item>
  <item rdf:about="http://dspace.dtu.ac.in:8080/jspui/handle/repository/13363">
    <title>MAJOR PROJECT KAYO-THE TRAFFIC MANAGER</title>
    <link>http://dspace.dtu.ac.in:8080/jspui/handle/repository/13363</link>
    <description>Title: MAJOR PROJECT KAYO-THE TRAFFIC MANAGER
Authors: SINGH, AMITOJ; DHILLON, AMRITPAL SINGH; SHARMA, GAURAV; CHADHA, VANEET
Description: BE THESIS</description>
    <dc:date>2006-01-31T00:00:00Z</dc:date>
  </item>
</rdf:RDF>

