Age | Commit message (Collapse) | Author | Files | Lines |
|
The postpone of close() is necessary to allow stuff like
$ses->send(..);
$link->close();
Since a ->send() uses postpone to queue the messages.
|
|
|
|
A bit more reliable than using an ID that may be re-used.
|
|
I find "node" to be much more descriptive for that. The Go
implementation hasn't been updated yet, though...
|
|
And removed the storable format from proto.pod. Looks like Storable has
a few annoying incompatibilities with different versions, so let's not
use it.
|
|
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.
|
|
|
|
|
|
|
|
|
|
Yay, this is the first complete and working implementation of the link
protocol! Not really final yet, though, but at least something to
experiment with.
|
|
|
|
|
|
The others are rather pointless.
|
|
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.
|