Data Transmission Using Multi-Tasking-Sockets

ABSTARCT:-This Project a new socket class which supports both TCP and UDP
communication. But it provides some advantages compared to other classes that you may find
here or on some other Socket Programming articles. First of all, this class doesn't have any
limitation like the need to provide a window handle to be used. This limitation is bad if all you
want is a simple console application. So this library doesn't have such a limitation. It also
provides threading support automatically for you, which handles the socket connection and
disconnection to a peer. It also features some options not yet found in any socket classes that I
have seen so far. It supports both client and server sockets. A server socket can be referred as to
a socket that can accept many connections. And a client socket is a socket that is connected to
server socket. You may still use this class to communicate between two applications without
establishing a connection. In the latter case, you will want to create two UDP server sockets (one
for each application). This class also helps reduce coding need to create chat-like applications
and IPC (Inter-Process Communication) between two or more applications (processes). Reliable
communication between two peers is also supported with TCP/IP with error handling. You may
want to use the smart addressing operation to control the destination of the data being transmitted
(UDP only). TCP operation of this class deals only with communication between two peers.

EXISTING SYSTEM: The thread is optional since the developer is still responsible to decide if
needs it. There are other Socket classes here and other places over the Internet but none of them
can provide feedback (event detection) to your application like this one does. It provides you
with the following events detection: connection established, connection dropped, connection
failed and data reception (including 0 byte packet).

PROPOSED SYSTEM: This article presents a new socket class which supports both TCP and
UDP communication. But it provides some advantages compared to other classes that you may
find here or on some other Socket Programming articles. First of all, this class doesn't have any
limitation like the need to provide a window handle to be used. This limitation is bad if all you
want is a simple console application. So this library doesn't have such a limitation. It also
provides threading support automatically for you, which handles the socket connection and
disconnection to a peer. It also features some options not yet found in any socket classes that I
have seen so far. It supports both client and server sockets. A server socket can be referred as to
a socket that can accept many connections. And a client socket is a socket that is connected to
server socket. You may still use this class to communicate between two applications without
establishing a connection. In the latter case, you will want to create two UDP server sockets (one
for each application). This class also helps reduce coding need to create chat-like applications
and IPC (Inter-Process Communication) between two or more applications (processes). Reliable
communication between two peers is also supported with TCP/IP with error handling. You may
want to use the smart addressing operation to control the destination of the data being transmitted
(UDP only). TCP operation of this class deals only with communication between two peers.

CreativeSoft (Corporate Office)

# 412, Annpurna Block,Aditya Enclave,Ameerpet,Hyderabad
500016 Tel : +91-40-40159158Mobile : 91-9247249455
Module Design Specification

part 1 - Create a server socket that listen for a client to connect

part 2 - send / receive data from client to server

part 3 - Read unknow size of data from client

part 1 Create a server socket that listens for a client to connect

socket(int af, int type, int protocol)

This method creates the socket

bind(SOCKET s, const struct sockaddr FAR * name, int namelen)

Associates a local address with a socket This routine is used on an unconnected

datagram or stream socket, before subsequent connects or listens. When a socket is
created with socket, it exists in a name space (address family), but it has no name
assigned. bind establishes the local association (host address/port number) of the socket
by assigning a local name to an unnamed socket. In the Internet address family, a name
consists of several components. For SOCK_DGRAM and SOCK_STREAM, the name
consists of three parts: a host address, the protocol number (set implicitly to UDP or
TCP, respectively), and a port number which identifies the application. If an
application does not care what address is assigned to it, it may specify an Internet
address equal to INADDR_ANY, a port equal to 0, or both. If the Internet address is
equal to INADDR_ANY, any appropriate network interface will be used; this
simplifies application programming in the presence of multi- homed hosts. If the port is
specified as 0, the Windows Sockets implementation will assign a unique port to the
application with a value between 1024 and 5000. The application may use getsockname
after bind to learn the address that has been assigned to it, but note that getsockname
will not necessarily fill in the Internet address until the socket is connected, since
several Internet addresses may be valid if the host is multi-homed. If no error occurs,
bind returns 0. Otherwise, it returns SOCKET_ERROR, and a specific error code may
be retrieved by calling WSAGetLastError.

listen(SOCKET s, int backlog )

Establishes a socket to listen to a incoming connection To accept connections, a

socket is first created with socket, a backlog for incoming connections is specified with
listen, and then the connections are accepted with accept. listen applies only to sockets
CreativeSoft (Corporate Office)
# 412, Annpurna Block,Aditya Enclave,Ameerpet,Hyderabad
500016 Tel : +91-40-40159158Mobile : 91-9247249455
 that support connections, i.e. those of type SOCK_STREAM. The socket s is put into
"passive'' mode where incoming connections are acknowledged and queued pending
acceptance by the process. This function is typically used by servers that could have
more than one connection request at a time: if a connection request arrives with the
queue full, the client will receive an error with an indication of
WSAECONNREFUSED. listen

attempts to continue to function rationally when there are no available descriptors.

It will accept connections until the queue is emptied. If descriptors become available, a
later call to listen or accept will re-fill the queue to the current or most recent
"backlog'', if possible, and resume listening for incoming connections.

accept(SOCKET s, struct sockaddr FAR * addr, int FAR * addrlen)

This routine extracts the first connection on the queue of pending connections on s,
creates a new socket with the same properties as s and returns a handle to the new
socket. If no pending connections are present on the queue, and the socket is not
marked as non- blocking, accept blocks the caller until a connection is present. If the
socket is marked non-blocking and no pending connections are present on the queue,
accept returns an error as described below. The accepted socket may not be used to
accept more connections. The original socket remains open. The argument addr is a
result parameter that is filled in with the address of the connecting entity, as known to
the communications layer. The exact format of the addr parameter is determined by the
address family in which the communication is occurring. The addrlen is a value-result
parameter; it should initially contain the amount of space pointed to by addr; on return
it will contain the actual length (in bytes) of the address returned. This call is used with
connection-based socket types such as SOCK_STREAM. If addr and/or addrlen are
equal to NULL, then no information about the remote address of the accepted socket is
returned.

closesocket(SOCKET s)

closes a socket

Making client connection with server

In order to create a socket that connects to an other socket uses most of the
functions from the previous code with the exception of a struct called HOSTENT

HOSTENT:

This struct is used to tell the socket to which computer and port to connect to.
These struct can appear as LPHOSTENT, but it actually means that they are pointer to
HOSTENT.

CreativeSoft (Corporate Office)

# 412, Annpurna Block,Aditya Enclave,Ameerpet,Hyderabad
500016 Tel : +91-40-40159158Mobile : 91-9247249455
 Client key function

Most of the functions that have been used for the client to connect to the server are
the same as the server with the exception of a few. I will just go through the different
functions that have been used for the client.

gethostbyname(const char* FAR name)

gethostbyname returns a pointer to a hostent structure as described under

gethostbyaddr. The contents of this structure correspond to the hostname name. The
pointer which is returned points to a structure which is allocated by the Windows
Sockets implementation. The application must never attempt to modify this structure or
to free any of its components. Furthermore, only one copy of this structure is allocated
per thread, and so the application should copy any information which it needs before
issuing any other Windows Sockets API calls. A gethostbyname implementation must
not resolve IP address strings passed to it. Such a request should be treated exactly as if
an unknown host name were passed. An application with an IP address string to resolve
should use inet_addr to convert the string to an IP address, then gethostbyaddr to obtain
the hostent structure.

Part 2 - Send / recieve

Up to this point we have managed to connect with our client to the server. Clearly
this is not going to be enough in a real-life application. In this section we are going to
look into more details how to use the send/recv functions in order to get some
communication going between the two applications.

Factually this is not going to be difficult because most of the hard work has been
done setting up the server and the client app. before going into the code we are going to
look into more details the two functions

send(SOCKET s, const char FAR * buf, int len, int flags)

send is used on connected datagram or stream sockets and is used to write outgoing
data on a socket. For datagram sockets, care must be taken not to exceed the maximum
IP packet size of the underlying subnets, which is given by the iMaxUdpDg element in
the WSAData structure returned by WSAStartup. If the data is too long to pass
atomically through the underlying protocol the error WSAEMSGSIZE is returned, and
no data is transmitted.

recv(SOCKET s, const char FAR * buf, int len, int flags)

CreativeSoft (Corporate Office)

# 412, Annpurna Block,Aditya Enclave,Ameerpet,Hyderabad
500016 Tel : +91-40-40159158Mobile : 91-9247249455
 For sockets of type SOCK_STREAM, as much information as is currently available
up to the size of the buffer supplied is returned. If the socket has been configured for
in- line reception of out-of-band data (socket option SO_OOBINLINE) and out-of-
band data is unread, only out-of-band data will be returned. The application may use
the ioctlsocket SIOCATMARK to determine whether any more out-of-band data
remains to be read.

part 3 - Read unknow size of data from client

Us mentioned earlier in part 2, we are noe going to expand on the way that we
receive data. The problem we had before is that if we did not know the size of data that
we where expecting, then the would end up with problems.

In order to fix this here we create a new function that receive a pointer to the client
socket, and then read a char at the time, placing each char into a vector until we find
the '\n' character that signifies the end of the message.

This solution is clearly not a robust or industrial way the read data from one socket
to an other, because but its a way to start reading unknown length strings. the function
will be called after the accept method

Requirement Specification:-

Software Requirement Specification:

Language: JDK1.3

Platform: Windows and Linux (platform Independent)

Client: Own Client designed Using Java Socket.

Server: Server designed Using Java Server Socket

Development Tool: JCreator.

Hardware Requirement Specification:

RAM: 128MB (Minimum).

Processor: Pentium 2 and above.

CreativeSoft (Corporate Office)

# 412, Annpurna Block,Aditya Enclave,Ameerpet,Hyderabad
500016 Tel : +91-40-40159158Mobile : 91-9247249455
 Processor Speed: Above 500 MHz.

CreativeSoft (Corporate Office)

# 412, Annpurna Block,Aditya Enclave,Ameerpet,Hyderabad
500016 Tel : +91-40-40159158Mobile : 91-9247249455