Age | Commit message (Collapse) | Author | Files | Lines |
|
I find "node" to be much more descriptive for that. The Go
implementation hasn't been updated yet, though...
|
|
This allows two unidirectional pipes (e.g. STDIN/STDOUT) to be used for
communication. There's no obvious or efficient way to combine two pipes
into a single AnyEvent::Handle.
|
|
|
|
|
|
|
|
The 'reply' thing is more typing overhead than it is worth. Especially
since the return-path functionality uses Perl's GC to automatically
close the return-path when no sessions have a reference to the object
anymore. A session can simply not read the second argument of the
tuple-callback to close the return path. (This does mean that the path
will stay open for as long as the function is running, but that doesn't
matter anyway in a single-threaded application.)
|
|
|
|
Note that I'm not even actually using AnyEvent functionality at the
moment. But no doubt I'm going to need it anyway.
|