00:05:15  * Fishrock123joined
00:11:13  * benjamingrquit (Quit: Connection closed for inactivity)
03:41:07  * brsonquit (Quit: leaving)
05:00:12  * Fishrock123quit (Quit: Leaving...)
06:04:21  * MoZu4k__joined
06:07:25  * etoquit (Quit: CyBrainCore:Leaving Matrix)
06:29:29  * MoZu4k__quit (Quit: MoZu4k__)
06:30:31  * rendarjoined
07:40:46  * seishunjoined
08:20:02  * rendarquit (Ping timeout: 268 seconds)
08:32:00  * rendarjoined
08:33:23  * seishunquit (Ping timeout: 245 seconds)
09:04:13  * a3fjoined
10:37:12  * a3fquit (Quit: Zzzzz..)
10:37:38  * a3fjoined
10:43:54  * a3fquit (Quit: Zzzzz..)
11:25:09  * thealphanerdquit (Quit: farewell for now)
11:25:40  * thealphanerdjoined
13:34:44  * nickleeflyjoined
14:00:55  * rmgquit (Remote host closed the connection)
14:52:05  * Fishrock123joined
15:41:42  * nickleeflyquit (Quit: Connection closed for inactivity)
16:27:29  * cremesquit (Quit: cremes)
16:29:00  * cremesjoined
16:37:16  * thefourtheyejoined
17:42:56  * rmgjoined
17:47:46  * seishunjoined
18:33:54  * zju1quit (Ping timeout: 256 seconds)
18:38:23  * seishunquit (Ping timeout: 245 seconds)
18:44:04  * seishunjoined
18:51:04  * zjujoined
21:10:47  * rendarquit (Quit: Leaving)
21:39:14  * tunniclmjoined
21:55:09  * grantilajoined
21:56:52  <grantila>I'm successfully reading with libuv I think, using uv_read_start and uv_read_stop to control how fast I can read in my application. But I find nothing for write. Am I missing something?
21:57:24  <grantila>Basically, if I'd just try (stumbling in darkness not knowing if I really can write) uv_try_write, and it returns UV_EAGAIN, what am I supposed to do?
22:00:12  <indutny>hello
22:00:20  <indutny>grantila: I won't go with uv_try_write for now
22:00:25  <indutny>especially if you are just learning things
22:00:31  <indutny>use `uv_write` instead
22:00:43  <indutny>`uv_try_write` is just a tool to optimize performance in some edge cases
22:00:59  <indutny>you don't need it at this point
22:02:10  <grantila>well, I don't want to end up filling internal buffers. I might send _fast_, and have my own application-level handling of streams with backpressure and everything, so I'd like to map that to libuv if possible.
22:15:50  <grantila>indutny: but even with `uv_write`, how do I handle when I can write more? Is that implicit when the callback is called - that I can write again?
22:16:58  <indutny>grantila: yep, this is true
22:17:02  <indutny>grantila: technically, you can queue as much as you want
22:17:11  <indutny>grantila: but when callback is called the data was dequeued to kernel
22:17:14  <indutny>so you can totally write more
22:19:50  <grantila>indutny: alright. well, queue as much as I want will fill up ram uncontrollably I guess. but this interface seems fair enough. What do I have to keep in memory for `uv_write`, only the pointers to the data (.base) or the actual uv_buf_t structs too?
22:20:22  <grantila>indutny: And the uv_write_t structs?
22:23:47  <indutny>grantila: just uv_write_t AFAIK
22:23:57  <indutny>brb
23:14:38  * seishunquit (Ping timeout: 245 seconds)
23:22:14  * italoacasasjoined
23:29:04  * grantilaquit (Quit: Leaving.)
23:42:28  * thefourtheyequit (Quit: Connection closed for inactivity)