EmbLogic's Blog

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

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]#

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>