10-24-2012
BTW, pipes do not buffer/delay write() data, but FILE* do delay output until you flush or overflow the buffer, unless you turn on unbuffered or line buffered output (setvbuf()). Graceful exit() flushes all pipes on all but the most crude C compilers.
Pipes are part of IPC, along with signals, shared memory, semaphores, message queues, mmap() of files, sockets. You can inherit a fd such as a pipe or socket from a parent. You can open a named pipe and if someone opens the opposite way (r/w), you are connected 1-1. BTW, you can pass fd down a pipe so another process can attach it. I prefer mmap(): no root requirement, all RAM as a buffer, hard copy after a crash and for a restart, no swap used. Some UNIX/LINUX flavors map socket resources into the file tree. UDP Sockets are neat, as they can broadcast and multicast. A really slick messaging app would multicast, so it scaled really well. When studying IPC, make sure your opinions do not come from way back. Systems have become quite different, and culturally, apps less root entangled.
10 More Discussions You Might Find Interesting
1. Programming
I have been trying to write a very basic chat program but at the moment I am having problems getting it to be multiuser as it closes all connections when one client shutsdown. I have also been having problems trying to get the program to display a list of usernames to the clients. I have tried... (0 Replies)
Discussion started by: dooker
0 Replies
2. Programming
Good day everyone,
I'm doing a chat client-server program:server is to receive messages from clients through a TCP port and multicast them back to all clients through a UDP port.
This is my client program. I'd not know why it just sends and receives msg from server once, then it stops.
Is... (1 Reply)
Discussion started by: powermind
1 Replies
3. Programming
here is the concept:
the client reads a pathname from the standard input and writes it to pipe1.The server reads this pathname from the pipe1 and tries to open the file for reading.If the server can open the file ,the server responds by reading the file and writting it to pipe2;otherwise the... (2 Replies)
Discussion started by: tolkki
2 Replies
4. UNIX for Dummies Questions & Answers
I want to make the following programm.
Using the server/client model I want 2 client to connect to the server then the server sends back to the clients the ip address and a number of a poort in order to open a udp connection between clients without using the server?
What I have done since now is... (2 Replies)
Discussion started by: kasma
2 Replies
5. Programming
How can i make two client to chat with each other.. without any work of server, i mean peer to peer i am making chat messenger on which all host will connect to/via server and if any host want private chat then thay work independently...
this is code(attached) which i have made for server... (1 Reply)
Discussion started by: bt87
1 Replies
6. UNIX for Dummies Questions & Answers
The task is to create a server client chat that contains a few basic safeguards against floods etc and which is capable of issuing at least one or two commands on the client computer. Working samples of such arrangements abound but freeware/shareware samples are not readily available. A catch in... (3 Replies)
Discussion started by: Bobby
3 Replies
7. Homework & Coursework Questions
request
create a chat system in linux where a user type smth and all the other users connected to server get the message.then a user have to create join leave or delete a channel of chat if he created it.i did the server and the client but i dont know how to implemt the chat rooms.i was ... (1 Reply)
Discussion started by: demonmind
1 Replies
8. Programming
I want to have a message send & receive through 2 half-duplex pipes
Flow of data
top half pipe
stdin--->parent(client) fd1--->pipe1-->child(server) fd1
bottom half pipe
child(server) fd2---->pipe2--->parent(client) fd2--->stdout
I need to have boundary structed message... (1 Reply)
Discussion started by: ouou
1 Replies
9. Programming
hello everyone,
i am making chat server in linux using c. i have made programs in which group chat can take place between multiple clients but i am not able to understand how to make 2 particular clients chat with each other. please help!!! (1 Reply)
Discussion started by: sweetbella
1 Replies
10. UNIX for Advanced & Expert Users
Besides talk and write are there any other good programs for talking to a particular user on the same Linux system. (1 Reply)
Discussion started by: cokedude
1 Replies
LEARN ABOUT ULTRIX
setbuffer
setbuf(3s) setbuf(3s)
Name
setbuf, setbuffer, setlinebuf, setvbuf - assign buffering to a stream
Syntax
#include <stdio.h>
void setbuf(stream, buf)
FILE *stream;
char *buf;
void setbuffer(stream, buf, size)
FILE *stream;
char *buf;
int size;
void setlinebuf(stream)
FILE *stream;
int setvbuf(stream, buf, type, size)
FILE *stream;
char *buf;
int type; size_t size;
Description
The three types of buffering available are unbuffered, block buffered, and line buffered. When an output stream is unbuffered, information
appears on the destination file or terminal as soon as written; when it is block buffered many characters are saved up and written as a
block; when it is line buffered characters are saved up until a new line is encountered or input is read from stdin. The routine may be
used to force the block out early. Normally all files are block buffered. For further information, see A buffer is obtained from upon the
first or on the file. If the standard stream stdout refers to a terminal it is line buffered. The standard stream stderr is always
unbuffered.
The routine is used after a stream has been opened but before it is read or written. The character array buf is used instead of an auto-
matically allocated buffer. If buf is the constant pointer NULL, input/output will be completely unbuffered. A manifest constant BUFSIZ
tells how big an array is needed:
char buf[BUFSIZ];
The routine, an alternate form of is used after a stream has been opened but before it is read or written. The character array buf whose
size is determined by the size argument is used instead of an automatically allocated buffer. If buf is the constant pointer NULL,
input/output will be completely unbuffered.
The routine is used to change stdout or stderr from block buffered or unbuffered to line buffered. Unlike and it can be used at any time
that the file descriptor is active.
The routine may be used after a stream has been opened but before it is read or written. Type determines how stream will be buffered.
Legal values for type, defined in stdio.h are:
_IOFBF causes input/output to be fully buffered.
_IOLBF causes output to be line buffered; the buffer will be flushed when a new line is written, the buffer is full, or input is
requested.
_IONBF causes input/output to be completely unbuffered.
If buf is not the NULL pointer, the array it points to will be used for buffering, instead of an automatically allocated buffer. The size
specifies the size of the buffer to be used. The constant BUFSIZ in <stdio.h> is suggested as a good buffer size. If input/output is
unbuffered, buf and size are ignored.
By default, output to a terminal is line buffered and all other input/output is fully buffered.
A file can be changed from unbuffered or line buffered to block buffered by using For further information, see A file can be changed from
block buffered or line buffered to unbuffered by using followed by with a buffer argument of NULL.
Restrictions
The standard error stream should be line buffered by default.
The and functions are not portable to non 4.2 BSD versions of UNIX.
See Also
malloc(3), fclose(3s), fopen(3s), fread(3s), getc(3s), printf(3s), putc(3s), puts(3s).
setbuf(3s)