So like what you all said it might be the reading part that is the the problem.
From what I think is just the read problem?
Reason is I comment the write link it just run the loop normally.
Suppose i am writing a C program which is going to use Socket calls. I want to use a Unix port for my Socket.
How can i determine a port which is not already in use? (1 Reply)
Hello,
I actually try to make client-server program.
I'm using SCO OpenServer Release 5.0.0 and when I try to compile my code (by TELNET) I've got this error :
I'm just using this simple code :
and I get the same error if I use :
If someone can help me,
Thanks (2 Replies)
Hi ,
I'm facing the following problem in socket programming.
My structure is
struct {
int i;
char *str;
}samp;
I'm creating the pointer to this structure and assigning the value to the structure members and send via the socket to the another process.
The receiver process when... (7 Replies)
Hello!:)
I'm trying to do some socket programming based on the following situation:
I have a directory service named Casino that will hold all the information regarding the gamers that will try to connect to it in order to play a game(for example (Blackjack).Once they make the login they are... (4 Replies)
Hello Everyone
Iam working on tcp/ip programming.with some time interval server has to send data.client has to close the connection and to open the connection between the time interval.this is the scenario
when iam closing the connection in client side the connection terminates.how to... (1 Reply)
i m using sockets for setting up a connection between a server and a client.
When the clients gets connected to the server, its ip is conveyed to the server through one of the predefined structures in c library...
i save this ip address in an array....1st client's ip address goes to the zeroth... (1 Reply)
Hi,
I have a client-server socket program. It has been working fine for over a year, but recently it started to show strange behavior.:confused:
After the server program runs for a while, it will show in the top command saying it is using lots of CPU, MEM. I assume it means the server code is... (1 Reply)
I'm using C/ C++ with gcc on Linux. I've a server socket where accept() is called on the socket inside a while() loop. The problem I am facing is that the first call to accept is blocking (i.e., the program waits for the first connection) but as soon as I fork afterwards (so that the child process... (2 Replies)
will there be any unexpected results on looping connect call for a non blocking socket to determine the connection based on error code. I am getting connection unsuccessful intermittently and so wondering whether is the timeout 500 millisec not sufficient or looping connect cause any unexpected.
... (7 Replies)
Discussion started by: satish@123
7 Replies
LEARN ABOUT DEBIAN
iv_task
iv_task(3) ivykis programmer's manual iv_task(3)NAME
iv_task_register, iv_task_unregister, iv_task_registered - deal with ivykis tasks
SYNOPSIS
#include <iv.h>
struct iv_task {
void *cookie;
void (*handler)(void *);
};
void IV_TASK_INIT(struct iv_task *task);
void iv_task_register(struct iv_task *task);
void iv_task_unregister(struct iv_task *task);
int iv_task_registered(struct iv_task *task);
DESCRIPTION
The functions iv_task_register and iv_task_unregister register, respectively unregister, a task with the current thread's ivykis event
loop. iv_task_registered on a task returns true if that task is currently registered with ivykis.
A task is like a timer, but with an immediate timeout. When a task is registered, unless it is unregistered again first, the callback
function specified by ->handler is guaranteed to be called once, in the thread that the task was registered in, some time after control
returns to the ivykis main loop but before ivykis will sleep for more events, with ->cookie as its first and sole argument. When this hap-
pens, the task is transparently unregistered.
Tasks are mainly used for scheduling code for execution where it is not appropriate to directly run that code in the calling context (for
example, because the current context might be run as a callback function where the caller expects certain conditions to remain invariant
after the callback completes).
The application is allowed to change the ->cookie and ->handler members at any time.
A given struct iv_task can only be registered in one thread at a time, and a task can only be unregistered in the thread that it was regis-
tered from.
There is no limit on the number of tasks registered at once.
See iv_examples(3) for programming examples.
SEE ALSO ivykis(3), iv_examples(3)ivykis 2010-08-15 iv_task(3)