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