10-01-2008
First of all, you don't "read" to the screen (or stdout), you "write" to it.
Second, I would store the number of bytes received in a variable. This way you don't need to use memset. Instead you can just set the last byte to zero.
Third, if you are already using c++ streams to write to stdout, you can also use an fstream to write into a file the same way.
10 More Discussions You Might Find Interesting
1. Programming
Hi !
I had a verry simple question to ask...
In unix when we create pipes.. the unnamed pipes that is...
is there any way to access those pipes outside the code ?
Another thing.. do sockets have an entry in the inode table ?
TIA,
Devyani. (1 Reply)
Discussion started by: devy8
1 Replies
2. Programming
I am looking for a way to have a program listen on a port (example: 8000) for communication I will be sending via that port to it(Linux Kernel machine). Once it recieves an appropiate command I need it to run a .bat file in linux.
I know what I need to do but I am running into a few problems:... (8 Replies)
Discussion started by: bigB8210
8 Replies
3. Programming
Hai,
How cani declare socket and collect the data in a string varialbe.
Since i am new to this i am asking this.
Can we connect multiple port.
Thank you. (6 Replies)
Discussion started by: arunkumar_mca
6 Replies
4. UNIX for Dummies Questions & Answers
how do i mointor how many sockets are opened from a particular foriegn address? (2 Replies)
Discussion started by: kirpond
2 Replies
5. Solaris
Is there a way to see what sockets are in use? The developers here are getting some defunct processes and they would like to get a socket list.
This is on a Solaris 8 machine.
Thanks! (1 Reply)
Discussion started by: kjbaumann
1 Replies
6. IP Networking
Is it possible to trace the packages and the statuses of client's and/or server's sockets by the UNIX network administrative tools?
Two applications interact via sockets. There is no problem if they stay in the same network segment. If their hosts connected through the firewall then they aren't... (4 Replies)
Discussion started by: gogogo
4 Replies
7. Programming
Hi,i now moved into a different section where i need to use sockets.
i am completely nill in sockets.
can some body please provide me what are the requirements for a socket.
to use sockets in c.
thanks (1 Reply)
Discussion started by: MrUser
1 Replies
8. Programming
if i have a server which wants to connect to exactly 5 clients, does that mean i need 5 socket file descriptors and use
listen(socket_fd,1);
for each one
or just do
listen(socket_fd,5)
also whats the second parameter number mean? what happens if i put 0 there?
also if i am connected... (28 Replies)
Discussion started by: omega666
28 Replies
9. Red Hat
hai guys,
I'm doing a project in which one server communicates with several clients. How can i do it when i have different port numbers???:confused: (0 Replies)
Discussion started by: rajeshb6
0 Replies
10. Programming
Hi, i am student, think learning about c++, someone has a example the how establish a conection with sockets :b::b: (1 Reply)
Discussion started by: mmartinez
1 Replies
XDoes*() XDoes*()
Name
XDoesBackingStore, XDoesSaveUnders, DoesBackingStore, DoesSaveUnders - query server support for backing store or save unders.
Synopsis
int XDoesBackingStore(screen)
Screen *screen;
Bool XDoesSaveUnders(screen)
Screen *screen;
Arguments
screen Specifies the appropriate Screen structure.
Returns
XDoesSaveUnders() returns True or False. XDoesBackingStore() returns WhenMapped, NotUseful, or Always.
Description
XDoesSaveUnders() returns a boolean value indicating whether the screen supports save unders. If True, the screen supports save unders.
If False, the screen does not support save unders.
XDoesBackingStore() returns a value indicating whether the screen supports backing stores. The value returned can be one of WhenMapped,
NotUseful, or Always.
Save unders and backing stores are optional server features controlled with window attributes. These macros tell you whether the server
supports them. A "save under" is an area beneath a window (usually a menu or dialog box) that the server saves, so that when the window is
removed from the screen, the underlying applications do not need to redraw their windows. This speeds up user response with a slight cost
in increased server memory consumption. A "backing store" is an off-screen copy of a window, maintained even when the window is not visi-
ble or not mapped. The server uses the copy to redraw the window whenever that window would otherwise have received an Expose event. This
reduces the load on applications at the expense of a possibly great increase in server memory usage.
The C language macros DoesSaveUnders() and DoesBackingStore() are equivalent and slightly more efficient.
See Also
XChangeWindowAttributes(), XGetWindowAttributes().
Xlib - Macro Equivalents XDoes*()