search for: shout_get_connect

Displaying 3 results from an estimated 3 matches for "shout_get_connect".

Did you mean: shout_get_connected
2004 Aug 06
1
libshout nonblocking API
...functions: int shout_set_nonblocking(shout_t *self, unsigned int nonblocking): Instructs libshout to use nonblocking I/O. Must be called before shout_open (no switching back and forth midstream at the moment). unsigned int shout_get_nonblocking(shout_t *self): self-explanatory. Changed functions: shout_get_connected: Will now attempt to complete login if the connection is in progress. May return additional error codes, or SHOUTERR_BUSY if the connection still hasn't finished opening. shout_open: May return SHOUTERR_BUSY as a non-fatal error. In this case, the client should call shout_get_connected() per...
2020 Apr 04
0
[PATCH] nonblocking: remove usleep usage
...0 @@ int main() if (ret == SHOUTERR_BUSY) printf("Connection pending...\n"); + const struct timespec req = {0, 10 * 1000 * 1000}; + struct timespec rem; while (ret == SHOUTERR_BUSY) { - usleep(10000); + nanosleep(&req, &rem); ret = shout_get_connected(shout); } -- 2.25.1
2008 Aug 30
3
Updated version of patch
Attached is a patch against shout-python-0.2 which does two trivial but very useful things (1) The function "get_connected" is exported so that shout-python becomes usable in nonblocking mode. In the current version of shout-python "open" raises an exception in nonblocking mode. (2) The global interpreter lock is released in the potentially blocking functions