AgeCommit message (Collapse)AuthorFilesLines
2012-04-20link: Postpone close() handling + don't push_shutdown() the read handlerHEADmasterYorhel1-3/+5
The postpone of close() is necessary to allow stuff like $ses->send(..); $link->close(); Since a ->send() uses postpone to queue the messages.
2012-04-17link: Don't attempt to write more stuff after closeYorhel1-0/+3
2012-04-05Build: Proper indentation + added JSON/JSON::XS as recommendationsYorhel1-12/+18
2012-03-22Added Build.PL to make this a proper distributable moduleYorhel1-0/+16
2012-03-22Added README and COPYING filesYorhel2-0/+36
2012-03-10Use ref-counted variable to detect whether pattern is unregisteredYorhel1-4/+6
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...
2012-02-22Allow user to specify supported serialization formatsYorhel1-8/+40
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.
2012-02-22Allow a different AnyEvent::Handle for reading and writingYorhel2-15/+27
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.
2012-02-22Updated Tanja::Link to use the new protocolYorhel2-12/+9
2012-02-19Implemented new proto + fixed many bugs; doc: Updated proto/JSONYorhel2-42/+131
2012-02-19s/response/reply/g + added a link test that currently still failsYorhel2-8/+28
2012-02-18Load AnyEvent::Handle and JSON/JSON::XS modules when neededYorhel1-10/+14
2012-02-18Implemented full link supportYorhel1-9/+95
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.
2012-02-17Add JSON serialization module + send register messages on connectYorhel1-2/+43
2012-02-17Started on Tanja::Link + implemented handshakingYorhel1-1/+60
2012-02-16Only 'use AnyEvent;' onceYorhel1-3/+9
The others are rather pointless.
2012-02-16Remove 'reply' argument + added return-path functionalityYorhel2-21/+60
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.)
2012-02-16Use AnyEvent::postpone() to make tuple dispatch asynchronousYorhel2-7/+12
2012-02-16Started on a simple Perl implementation (using AnyEvent)Yorhel2-0/+221
Note that I'm not even actually using AnyEvent functionality at the moment. But no doubt I'm going to need it anyway.