[ccan] ccan: the psuedo "networking" module.

[Allan Ference]

Hey Rusty,

Got a few questions if you don't mind:
On Tue, Dec 4, 2012 at 2:14 AM, Rusty Russell <rusty at rustcorp.com.au> wrote:
>
>         /* Useful next functions. */
>         /* Close the connection, we're done. */
>         void next_close(struct conn *, void *arg));
>
> I'm not quite sure what this should do exactly, it may sound stupid but,
is it supposed to close the conn specified next time activity comes through
it?

> The best thing is that you could force the implementation into a
> debugging sychronous mode, where conn_read_* and conn_write_* worked
> synchonously, and conn_next immediately called the next function.  This
> gives you a nice call-chain to see exactly what occurred.
>
> So the only part that's supposed to work asynchronously is the server,
right?
I also don't quite get the idea here, shall we make every incoming
connections BLOCKING and not add it to the polling queue?!

Please answer briefly, and I will finish it as soon as possible (2 days at
max).

Thanks,
Allan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/ccan/attachments/20121220/a0cb0f62/attachment.html>