EmbLogic's Blog

Inter process communication using fifo at the requesting side and pipes at the processing side using semaphores and signals.

RCS file: header.h,v
Working file: header.h
head: 1.1
branch:
locks: strict
psingh: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1;    selected revisions: 1
description:
gave header files which are required for the fifo and semaphore implementation.
gave prototypes for the request structure
gave prototype for the semaphore union
gave prototypes for the invoke_process functions
—————————-
revision 1.1    locked by: psingh;
date: 2015/04/03 18:51:58;  author: psingh;  state: Exp;
Initial revision
=============================================================================

RCS file: c1.c,v
Working file: c1.c
head: 1.1
branch:
locks: strict
psingh: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1;    selected revisions: 1
description:
thi is first requesting client
here request for addition is sent to the server side
including semaphores and signals
request has been sent through the fifo to the server
—————————-
revision 1.1    locked by: psingh;
date: 2015/04/03 18:51:58;  author: psingh;  state: Exp;
Initial revision
=============================================================================

RCS file: c2.c,v
Working file: c2.c
head: 1.1
branch:
locks: strict
psingh: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1;    selected revisions: 1
description:
this is second requesting client
here request for subtraction sent to server side
using semaphores and signals
request sent through fifo
result read through another fifo
—————————-
revision 1.1    locked by: psingh;
date: 2015/04/03 18:51:58;  author: psingh;  state: Exp;
Initial revision
=============================================================================

RCS file: c3.c,v
Working file: c3.c
head: 1.1
branch:
locks: strict
psingh: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1;    selected revisions: 1
description:
this is third requesting client
here request for multiplication sent thorugh fifo to the server side
using semaphores and signals
result read through another fifo from the server’s end
—————————-
revision 1.1    locked by: psingh;
date: 2015/04/03 18:51:58;  author: psingh;  state: Exp;
Initial revision
=============================================================================

RCS file: p1.c,v
Working file: p1.c
head: 1.1
branch:
locks: strict
psingh: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1;    selected revisions: 1
description:
this is the processing client
here addition operation is performed on the request sent by the requesting client
result is send through the pipe to the servers end using signals
—————————-
revision 1.1    locked by: psingh;
date: 2015/04/03 18:51:58;  author: psingh;  state: Exp;
Initial revision
=============================================================================

RCS file: p2.c,v
Working file: p2.c
head: 1.1
branch:
locks: strict
psingh: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1;    selected revisions: 1
description:
this is the second processing client
here subtraction operation is performed on the request sent by the requesting client
result is sent back to the server’s end using pipes and signals
—————————-
revision 1.1    locked by: psingh;
date: 2015/04/03 18:51:58;  author: psingh;  state: Exp;
Initial revision
=============================================================================

RCS file: p3.c,v
Working file: p3.c
head: 1.1
branch:
locks: strict
psingh: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1;    selected revisions: 1
description:
this is third processing client
here operation of multiplication is performed on the request sent by the requsting client
result is sent back to the server using pipes and signals
—————————-
revision 1.1    locked by: psingh;
date: 2015/04/03 18:51:58;  author: psingh;  state: Exp;
Initial revision
=============================================================================

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>