EmbLogic » Project 04: FTP based Client Server using Threads and Sockets

Socket programming based Home Automation

Raghu Nath — Fri, 09 Dec 2016 12:04:21 +0000

The main aim of this project is to implement Socket programming using Embedded linux based boards using beagle bone as server and pc as a client. The entire electrical system like home appliances are interfaced to Server (Beagle bone black) using relay electronics system.There will be authentication system for accessing the server like user id and password which will be provided by user through client.The enhancement of authentication system will be based on shell scripts.The user can control any appliance at any time from linux terminal.The user will run application based code which is interfaced to the Client program by providing basic authentication. An acknowledgement is also provided to user to monitor the status of the Appliance by server.The protocol used here is TCP (Transmission Control protocol)Client Server model, The Client will send the request to server.The Server process takes a request from the client. After getting a request from the client, this process will perform the required processing, gather the requested information, and send it to the requester client. The user will provide some input data by command line arguments to application Client.The beagle bone Server application will be automated after initial boot power-on with the help of bashRC Scripting.

client-server program using AF_UNIX

Jyoti Singh — Sun, 03 Apr 2016 15:37:46 +0000

RCS file: header.h,v
Working file: header.h
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
This is the base header file for the Project
—————————-
revision 1.1 locked by: root;
date: 2016/04/03 15:35:50; author: root; state: Exp;
Initial revision
=============================================================================RCS file: req_client.c,v
Working file: req_client.c
head: 1.2
branch:
locks: strict
root: 1.2
access list:
symbolic names:
keyword substitution: kv
total revisions: 2; selected revisions: 2
description:
This is the requesting client …sending request to the server.
Has socket() to creat the socket.
Has the connect() to connect to the server.
—————————-
revision 1.2 locked by: root;
date: 2015/06/18 09:04:22; author: root; state: Exp; lines: +7 -1
client has entered some data …into the buffer…and send that buffer through the socket file discriptor.
write()is used to wrote data
—————————-
revision 1.1
date: 2015/06/18 07:20:19; author: root; state: Exp;
Initial revision
=============================================================================RCS file: srvr.c,v
Working file: srvr.c
head: 1.4
branch:
locks: strict
root: 1.4
access list:
symbolic names:
keyword substitution: kv
total revisions: 4; selected revisions: 4
description:
this is my server program for socket programming.
this includes socket()to create the socket and returns file discriptor.
then there is bind call to name the socket created.
—————————-
revision 1.4 locked by: root;
date: 2016/01/29 08:41:59; author: root; state: Exp; lines: +36 -25
Used remove instead of unlink
used strncpy insted of strcpy to maintain the portability.
—————————-
revision 1.3
date: 2015/06/18 09:05:59; author: root; state: Exp; lines: +16 -2
the data accepted by the accept()call .
read and print the data
—————————-
revision 1.2
date: 2015/06/18 06:37:40; author: root; state: Exp; lines: +27 -7
Created listen() to listen the accept and given backlog value as 10.that is listen queue size
created accept() to accept the request of the client
—————————-
revision 1.1
date: 2015/06/18 05:55:53; author: root; state: Exp;
Initial revision
=============================================================================

Basic_program of socket

Sanjay Singla — Mon, 29 Feb 2016 06:03:11 +0000

server_program

int main()
9 {
10 int s_sockfd,c_sockfd;
11 int c_len,s_len,s_result;
12 struct sockaddr_un s_address;
13 struct sockaddr_un c_address;
14 unlink(“emblogic”);
15 s_sockfd = socket(AF_UNIX,SOCK_STREAM,0);
16 printf(“Print the s_sockfd %d\n”,s_sockfd);
17 if(s_sockfd == -1)
18 {
19 perror(“Error due to fd\n”);
20 exit(EXIT_FAILURE);
21 }
22 s_address.sun_family = AF_UNIX;
23 strcpy(s_address.sun_path,”emblogic”);
24 s_len = sizeof(s_address);
25 bind(s_sockfd,(struct sockaddr*)&s_address,s_len);
26 listen(s_sockfd,5);
27 while(1)
28 {
29 char ch;
30 printf(“Server is waiting\n”);
31 c_len = sizeof(c_address);
32 c_sockfd = accept(s_sockfd,(struct sockaddr*)&c_address,&c_len);
33 if(c_sockfd == -1)
34 {
35 perror(“Error due the accept call\n”);
36 exit(EXIT_FAILURE);
37 }
38 read(c_sockfd,&ch,1);
39 printf(“Print the value of ch–>>%c\n”,ch);
40 ch++;
41 write(c_sockfd,&ch,1);
42 close(c_sockfd);
43 }
44 return 0;
45 }

client_program

1 #include
2 #include
3 #include
4 #include
5 #include
6 #include
7 #include
8 int main()
9 {
10 int sockfd;
11 int len,result;
12 struct sockaddr_un address;
13 char ch = ‘A’;
14 sockfd = socket(AF_UNIX,SOCK_STREAM,0);
15 printf(“Print the client sockfd–>>>%d\n”,sockfd);
16 if(sockfd < 0)
17 {
18 perror(“Error due the sockfd\n”);
19 exit(EXIT_FAILURE);
20 }
21 address.sun_family = AF_UNIX;
22 strcpy(address.sun_path,”emblogic”);
23 len = sizeof(address);
24 result = connect(sockfd,(struct sockaddr*)&address,len);
25 if(result == -1)
26 {
27 perror(“Error due the client1\n”);
28 exit(EXIT_FAILURE);
29 }
30 write(sockfd,&ch,1);
31 read(sockfd,&ch,1);
32 printf(“Char in server=%c\n”,ch);
33 close(sockfd);
34 return 0;
35 }
~

Sockets – Basics

Ankur Garg — Sun, 31 Jan 2016 09:29:56 +0000

Sockets
=======
A socket is a communication mechanism that allows client/server systems to be developed either locally,on a single machine, or across networks.
- It is a communication mechanism
- It allows client/server systems to developed either locally or across a network.
- Socket is an extension of pipe
- They make clear distinction between client and server.
- Socket can be named or unnamed.
- They make clear distinction between server and client.
- In a socket, one side is client/server for read/write/both and other side is a network interface.

There are 6 tasks in a socket :-
1. Create Socket.
2. Give name to socket.
3. Listen to socket for incoming connection.
4. Coonect the client to server.
5. Accept the request by server from client.
6. Close the socket

Estblished full duplex communication between client and server using socket with domain AF_INET

Vineet — Mon, 20 Apr 2015 05:48:31 +0000

RCS file: client.c,v
Working file: client.c
head: 1.4
branch:
locks: strict
root: 1.4
access list:
symbolic names:
keyword substitution: kv
total revisions: 4; selected revisions: 4
description:
Thie is the base file for client for full duplex communication between client and server using socket whith domain AF_INET.
created socket using socket system call.
—————————-
revision 1.4 locked by: root;
date: 2015/04/20 05:45:35; author: root; state: Exp; lines: +0 -1
successfully received data from server.
—————————-
revision 1.3
date: 2015/04/20 05:41:41; author: root; state: Exp; lines: +0 -1
successfully connected to server.
sending data to server from stdin.
—————————-
revision 1.2
date: 2015/04/20 05:38:26; author: root; state: Exp; lines: +1 -0
used connect system call to establish a connection with the server.
waiting for server to accept the connection reuest.
—————————-
revision 1.1
date: 2015/04/20 05:20:01; author: root; state: Exp;
Initial revision
=============================================================================

RCS file: server.c,v
Working file: server.c
head: 1.4
branch:
locks: strict
root: 1.4
access list:
symbolic names:
keyword substitution: kv
total revisions: 4; selected revisions: 4
description:
This is the base file for server full duplex communication between client and server using socket whith domain AF_INET.
Created socket using socket syetem call.
—————————-
revision 1.4 locked by: root;
date: 2015/04/20 05:44:22; author: root; state: Exp; lines: +0 -1
Succssfully received data from clinet.
replying back client with stdin.
—————————-
revision 1.3
date: 2015/04/20 05:41:03; author: root; state: Exp; lines: +0 -1
used accept call to get the connection request from client.
Successfully connected to client.
—————————-
revision 1.2
date: 2015/04/20 05:20:52; author: root; state: Exp; lines: +1 -0
used bind call to assign address to socket.
used listen call to create listen queue.
—————————-
revision 1.1
date: 2015/04/20 05:20:01; author: root; state: Exp;
Initial revision
=============================================================================

Estblished Half duplex communication between client and server using socket with domain AF_INET

Vineet — Mon, 20 Apr 2015 05:44:20 +0000

RCS file: client.c,v
Working file: client.c
head: 1.4
branch:
locks: strict
root: 1.4
access list:
symbolic names:
keyword substitution: kv
total revisions: 4; selected revisions: 4
description:
Thie is the base file for client for half duplex communication between client and server using socket whith domain AF_INET.
created socket using socket system call.
—————————-
revision 1.4 locked by: root;
date: 2015/04/20 05:45:35; author: root; state: Exp; lines: +0 -1
successfully received data from server.
—————————-
revision 1.3
date: 2015/04/20 05:41:41; author: root; state: Exp; lines: +0 -1
successfully connected to server.
sending data to server from stdin.
—————————-
revision 1.2
date: 2015/04/20 05:38:26; author: root; state: Exp; lines: +1 -0
used connect system call to establish a connection with the server.
waiting for server to accept the connection reuest.
—————————-
revision 1.1
date: 2015/04/20 05:20:01; author: root; state: Exp;
Initial revision
=============================================================================

RCS file: server.c,v
Working file: server.c
head: 1.4
branch:
locks: strict
root: 1.4
access list:
symbolic names:
keyword substitution: kv
total revisions: 4; selected revisions: 4
description:
This is the base file for server half duplex communication between client and server using socket whith domain AF_INET.
Created socket using socket syetem call.
—————————-
revision 1.4 locked by: root;
date: 2015/04/20 05:44:22; author: root; state: Exp; lines: +0 -1
Succssfully received data from clinet.
replying back client with stdin.
—————————-
revision 1.3
date: 2015/04/20 05:41:03; author: root; state: Exp; lines: +0 -1
used accept call to get the connection request from client.
Successfully connected to client.
—————————-
revision 1.2
date: 2015/04/20 05:20:52; author: root; state: Exp; lines: +1 -0
used bind call to assign address to socket.
used listen call to create listen queue.
—————————-
revision 1.1
date: 2015/04/20 05:20:01; author: root; state: Exp;
Initial revision
=============================================================================

Successfully implemented Simplex communication between client and server using sockets with domain AF_UNIX.

Vineet — Sun, 19 Apr 2015 07:25:11 +0000

RCS file: server.c,v
Working file: server.c
head: 1.4
branch:
locks: strict
root: 1.4
access list:
symbolic names:
keyword substitution: kv
total revisions: 4; selected revisions: 4
description:
This is the base file for server for client-server communication using sockets.
—————————-
revision 1.4 locked by: root;
date: 2015/04/19 07:25:24; author: root; state: Exp; lines: +1 -2
Successfully received string from the client.
Successfully established a SIMPLEX COMMUNICATION between client and server.
—————————-
revision 1.3
date: 2015/04/19 07:23:38; author: root; state: Exp; lines: +0 -1
Successfully connected to the client.
Waiting for client to send the data.
/
—————————-
revision 1.2
date: 2015/04/19 07:20:52; author: root; state: Exp; lines: +1 -0
Created Socket using socket() function call.
Created queue using listen call.
Used Bind call and Accept call to accept the request from client.
waiting for client to send the request.
—————————-
revision 1.1
date: 2015/04/19 07:17:20; author: root; state: Exp;
Initial revision
=============================================================================

RCS file: client.c,v
Working file: client.c
head: 1.4
branch:
locks: strict
root: 1.4
access list:
symbolic names:
keyword substitution: kv
total revisions: 4; selected revisions: 4
description:
Created socket and sent connection request to server.
—————————-
revision 1.4 locked by: root;
date: 2015/04/19 07:26:36; author: root; state: Exp; lines: +0 -1
Able to send data continuously unless server says “bye” to end the comion
—————————-
revision 1.3
date: 2015/04/19 07:24:16; author: root; state: Exp; lines: +0 -1
Got input from the user from stdin (Keyboard).
stored it in a buffer and sent to server.
—————————-
revision 1.2
date: 2015/04/19 07:22:53; author: root; state: Exp; lines: +1 -0
Sent connection request.
connected to server successfully.
—————————-
revision 1.1
date: 2015/04/19 07:19:17; author: root; state: Exp;
Initial revision
=============================================================================

socket using AF_INET

Ashish Gupta — Sat, 11 Apr 2015 06:54:44 +0000

RCS file: server_inet.c,v
Working file: server_inet.c
head: 1.8
branch:
locks: strict
root: 1.8
access list:
symbolic names:
keyword substitution: kv
total revisions: 8; selected revisions: 8
description:
this the file for srver
—————————-
revision 1.8 locked by: root;
date: 2015/04/11 06:49:58; author: root; state: Exp; lines: +1 -1
here now,performing the reading
—————————-
revision 1.7
date: 2015/04/11 06:47:43; author: root; state: Exp; lines: +1 -1
here givingf the accept(),so that a particular socket can be created for processing the particular req from the client side
this call will creat the socket that would connect to that particular req
—————————-
revision 1.6
date: 2015/04/11 06:45:31; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.5
date: 2015/04/11 06:44:31; author: root; state: Exp; lines: +2 -2
giving the listen(),so that the reaquest from the side of the client can be listed in the list queue
—————————-
revision 1.4
date: 2015/04/11 06:42:56; author: root; state: Exp; lines: +2 -2
giving the socket call
so that a socket will be created which will return a socket fd
giving the bind call,which will give the name to the socket which we have been created,
so the socket created here will be the named socket
—————————-
revision 1.3
date: 2015/04/11 06:42:15; author: root; state: Exp; lines: +1 -1
defining the structure variables sin.family,port and addr
—————————-
revision 1.2
date: 2015/04/11 06:40:39; author: root; state: Exp; lines: +1 -1
included the header files
defining the variables
—————————-
revision 1.1
date: 2015/04/11 06:39:30; author: root; state: Exp;
Initial revision
=============================================================================

socket using AF_UNIX

Ashish Gupta — Mon, 30 Mar 2015 08:08:40 +0000

head 1.6;
access;
symbols;
locks
ashish:1.6; strict;
comment @ * @;

1.6
date 2015.03.29.13.01.22; author ashish; state Exp;
branches;
next 1.5;

1.5
date 2015.03.29.12.57.43; author ashish; state Exp;
branches;
next 1.4;

1.4
date 2015.03.29.12.56.00; author ashish; state Exp;
branches;
next 1.3;

1.3
date 2015.03.29.12.54.16; author ashish; state Exp;
branches;
next 1.2;

1.2
date 2015.03.29.12.44.26; author ashish; state Exp;
branches;
next 1.1;

1.1
date 2015.03.29.12.40.43; author ashish; state Exp;
branches;
next ;

desc
@showing communication between two file using socket by using AF_UNIX
@

1.6
log
@in the similar way..the more client can be connected

1.5
log
@now giving the connect(),call at the client side so that the req of client that can be for read or write operation,can be listen at the side of server
at the server giving the accept() call,where it creat the copy of socket created above but that would be unnamed,so that created socket will coonected to that particular client for the req came from the client
@
text
@d28 1
@

1.4
log
@now giving a call for listen,by using listen()
so that the req from the client side can be listen by server
with this call a listen queue will be created
where the req from client will be taken
@
text
@d23 1
a23 1

1.3
log
@giving the socket family and its path
socket have been created
now giving the name to the socket by using bind(),call,now the socket in the server have been created as nameed socket
same socket have been created in the client side,but that s unmaed
@
text
@d23 1
a23 1

1.2
log
@includeng the header files
creating the socket by giving the socket(),where we are using the family AF_UNIX
@
text
@d12 1
a12 1

1.1
log
@Initial revision
@
text
@d12 1
a12 1

IPC based server-client project using a multithreaded server(test with more than 140000 requests at a time)

Vipin Choudhary — Fri, 21 Nov 2014 19:55:29 +0000

RCS file: server.c,v
Working file: server.c
head: 1.48
branch:
locks: strict
root: 1.48
access list:
symbolic names:
keyword substitution: kv
total revisions: 48; selected revisions: 48
description:
server code scp project
—————————-
revision 1.48 locked by: root;
date: 2014/11/21 06:10:31; author: root; state: Exp; lines: +7 -7
implement multithread server for any number of request successfuly and test with 140000 requests..
—————————-
revision 1.47
date: 2014/11/21 06:04:31; author: root; state: Exp; lines: +7 -7
*** empty log message ***
—————————-
revision 1.46
date: 2014/11/21 05:34:31; author: root; state: Exp; lines: +7 -7
*** empty log message ***
—————————-
revision 1.45
date: 2014/11/21 04:45:07; author: root; state: Exp; lines: +7 -7
*** empty log message ***
—————————-
revision 1.44
date: 2014/11/21 04:32:55; author: root; state: Exp; lines: +7 -7
*** empty log message ***
—————————-
revision 1.43
date: 2014/11/21 04:12:48; author: root; state: Exp; lines: +0 -2
*** empty log message ***
—————————-
revision 1.42
date: 2014/11/21 04:10:04; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.41
date: 2014/11/21 04:04:15; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.40
date: 2014/11/21 03:55:52; author: root; state: Exp; lines: +2 -0
*** empty log message ***
—————————-
revision 1.39
date: 2014/11/21 03:53:17; author: root; state: Exp; lines: +5 -2
*** empty log message ***
—————————-
revision 1.38
date: 2014/11/21 03:48:59; author: root; state: Exp; lines: +0 -1
*** empty log message ***
—————————-
revision 1.37
date: 2014/11/21 03:48:13; author: root; state: Exp; lines: +0 -2
*** empty log message ***
—————————-
revision 1.36
date: 2014/11/21 03:46:47; author: root; state: Exp; lines: +15 -0
*** empty log message ***
—————————-
revision 1.35
date: 2014/11/21 03:39:26; author: root; state: Exp; lines: +1 -0
*** empty log message ***
—————————-
revision 1.34
date: 2014/11/21 03:35:44; author: root; state: Exp; lines: +2 -2
*** empty log message ***
—————————-
revision 1.33
date: 2014/11/21 03:31:06; author: root; state: Exp; lines: +1 -2
*** empty log message ***
—————————-
revision 1.32
date: 2014/11/21 03:30:20; author: root; state: Exp; lines: +4 -2
*** empty log message ***
—————————-
revision 1.31
date: 2014/11/21 00:57:59; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.30
date: 2014/11/21 00:56:40; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.29
date: 2014/11/21 00:56:13; author: root; state: Exp; lines: +3 -1
*** empty log message ***
—————————-
revision 1.28
date: 2014/11/21 00:51:53; author: root; state: Exp; lines: +4 -1
implement a logic that allow a perticular thread reusable if it is terminated.
—————————-
revision 1.27
date: 2014/11/21 00:28:31; author: root; state: Exp; lines: +4 -4
*** empty log message ***
—————————-
revision 1.26
date: 2014/11/20 20:56:50; author: root; state: Exp; lines: +4 -4
*** empty log message ***
—————————-
revision 1.25
date: 2014/11/20 20:42:26; author: root; state: Exp; lines: +4 -4
rearrange server for 500 request
—————————-
revision 1.24
date: 2014/11/20 19:29:51; author: root; state: Exp; lines: +4 -4
*** empty log message ***
—————————-
revision 1.23
date: 2014/11/20 17:05:27; author: root; state: Exp; lines: +5 -1
*** empty log message ***
—————————-
revision 1.22
date: 2014/11/20 16:55:02; author: root; state: Exp; lines: +8 -8
*** empty log message ***
—————————-
revision 1.21
date: 2014/11/20 16:52:29; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.20
date: 2014/11/20 16:52:05; author: root; state: Exp; lines: +3 -2
*** empty log message ***
—————————-
revision 1.19
date: 2014/11/20 16:47:18; author: root; state: Exp; lines: +10 -5
*** empty log message ***
—————————-
revision 1.18
date: 2014/11/20 15:17:24; author: root; state: Exp; lines: +5 -5
*** empty log message ***
—————————-
revision 1.17
date: 2014/11/20 15:15:07; author: root; state: Exp; lines: +5 -5
implement a logic to get the accurate result at corresponding req. client
/
—————————-
revision 1.16
date: 2014/11/20 06:35:32; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.15
date: 2014/11/20 06:23:51; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.14
date: 2014/11/20 06:22:08; author: root; state: Exp; lines: +0 -1
*** empty log message ***
—————————-
revision 1.13
date: 2014/11/20 06:21:34; author: root; state: Exp; lines: +9 -3
*** empty log message ***
—————————-
revision 1.12
date: 2014/11/20 03:50:38; author: root; state: Exp; lines: +14 -10
imlement the semaphore in requesting client to send data in message queue one by one
—————————-
revision 1.11
date: 2014/11/20 02:23:30; author: root; state: Exp; lines: +5 -0
*** empty log message ***
—————————-
revision 1.10
date: 2014/11/20 02:15:11; author: root; state: Exp; lines: +5 -5
implemented server for multirequest successfully and get the right results
now i m going to check the need of request synchronization.
—————————-
revision 1.9
date: 2014/11/20 01:31:11; author: root; state: Exp; lines: +7 -7
implement logic to receive data structure in the treads
—————————-
revision 1.8
date: 2014/11/20 01:13:05; author: root; state: Exp; lines: +48 -4
implement operand filter using switch and case statements
send the result in message queue with a appropriate key
—————————-
revision 1.7
date: 2014/11/20 00:18:43; author: root; state: Exp; lines: +2 -2
*** empty log message ***
—————————-
revision 1.6
date: 2014/11/20 00:05:48; author: root; state: Exp; lines: +8 -7
implement the logic to get multi request and process them simultaneously by using multi thread
—————————-
revision 1.5
date: 2014/11/18 22:57:40; author: root; state: Exp; lines: +4 -4
*** empty log message ***
—————————-
revision 1.4
date: 2014/11/18 22:55:43; author: root; state: Exp; lines: +2 -1
call msgget and msgctl function
—————————-
revision 1.3
date: 2014/11/18 22:54:24; author: root; state: Exp; lines: +1 -1
add header file in server for threads
—————————-
revision 1.2
date: 2014/11/18 22:52:36; author: root; state: Exp; lines: +15 -71
design server using threads
—————————-
revision 1.1
date: 2014/11/18 20:12:55; author: root; state: Exp;
Initial revision
=============================================================================
[root@VIPIN scp_using_threads3]#

Basic implementation of Treads

Vipin Choudhary — Fri, 21 Nov 2014 19:43:19 +0000

RCS file: ./1_basicimpof_creat_join_exit.c,v
Working file: ./1_basicimpof_creat_join_exit.c
head: 1.2
branch:
locks: strict
root: 1.2
access list:
symbolic names:
keyword substitution: kv
total revisions: 2; selected revisions: 2
description:
Basic implementation of threads
—————————-
revision 1.2 locked by: root;
date: 2014/11/22 04:45:10; author: root; state: Exp; lines: +3 -3
implement the pthread_create,pthread_join and pthread _exit call
—————————-
revision 1.1
date: 2014/11/22 04:43:51; author: root; state: Exp;
Initial revision
=============================================================================
[root@VIPIN basic_imp]#

Chat box implementation by socket(loop back)

Vipin Choudhary — Fri, 21 Nov 2014 19:39:33 +0000

RCS file: ./ser_socket.c,v
Working file: ./ser_socket.c
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
Chat box implementation by socket using loopback
implement socket,listen,accept system call to get connection
—————————-
revision 1.1 locked by: root;
date: 2014/11/22 06:00:14; author: root; state: Exp;
Initial revision
=============================================================================

RCS file: ./sock_client.c,v
Working file: ./sock_client.c
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
implement socket and connect call to establised connection
implement message read and write operation in infinite loop
—————————-
revision 1.1 locked by: root;
date: 2014/11/22 06:00:14; author: root; state: Exp;
Initial revision
=============================================================================
[root@VIPIN socket_loopback]#

Communication between client and server through socket with Domain-AF_INET

Md. Isharat — Fri, 07 Nov 2014 12:31:36 +0000

RCS file: RCS/server.c,v
Working file: server.c
head: 1.6
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 6; selected revisions: 6
description:
main server file
Include socket.h and types.h
—————————-
revision 1.6
date: 2014/11/06 05:25:09; author: root; state: Exp; lines: +10 -7
make server in while 1
—————————-
revision 1.5
date: 2014/11/05 07:16:21; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.4
date: 2014/11/04 12:11:14; author: root; state: Exp; lines: +1 -0
server write after reading from client
—————————-
revision 1.3
date: 2014/11/04 12:02:06; author: root; state: Exp; lines: +1 -0
use perror after listen call
—————————-
revision 1.2
date: 2014/11/04 12:00:45; author: root; state: Exp; lines: +32 -1
done
—————————-
revision 1.1
date: 2014/11/04 10:35:37; author: root; state: Exp;
Initial revision
=============================================================================

RCS file: RCS/client.c,v
Working file: client.c
head: 1.4
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 4; selected revisions: 4
description:
1st client file
include header file
—————————-
revision 1.4
date: 2014/11/06 05:25:29; author: root; state: Exp; lines: +11 -5
usr will enter the data to send
“close” will terminate the communication
—————————-
revision 1.3
date: 2014/11/04 12:11:33; author: root; state: Exp; lines: +3 -0
client read after writing
—————————-
revision 1.2
date: 2014/11/04 12:00:54; author: root; state: Exp; lines: +16 -1
done
—————————-
revision 1.1
date: 2014/11/04 10:36:10; author: root; state: Exp;
Initial revision

communication between client and server(Both on different system) through socket with Domain-AF_INET

Joon Vichitra — Thu, 06 Nov 2014 05:33:36 +0000

Done: client-server using AF_INET on the same system using loopback

Joon Vichitra — Tue, 04 Nov 2014 12:06:36 +0000

RCS file: RCS/server.c,v
Working file: server.c
head: 1.3
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 3; selected revisions: 3
description:
main server file
Include socket.h and types.h
—————————-
revision 1.3
date: 2014/11/04 12:02:06; author: root; state: Exp; lines: +1 -0
use perror after listen call
—————————-
revision 1.2
date: 2014/11/04 12:00:45; author: root; state: Exp; lines: +32 -1
done
—————————-
revision 1.1
date: 2014/11/04 10:35:37; author: root; state: Exp;
Initial revision
=============================================================================

RCS file: RCS/client.c,v
Working file: client.c
head: 1.2
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 2; selected revisions: 2
description:
1st client file
include header file
—————————-
revision 1.2
date: 2014/11/04 12:00:54; author: root; state: Exp; lines: +16 -1
done
—————————-
revision 1.1
date: 2014/11/04 10:36:10; author: root; state: Exp;
Initial revision
==================================================================