Comments on: First Steps with AnyEvent

By: Andres

Andres — Tue, 10 Jul 2012 15:03:04 +0000

Sorry guys, my mistake. It does accept multiple connections. Trick is not to overwirte or outscope $headers_io_watcher (as mentioned in the original post).
What I was trying to do was to save the $headers_io_watcher into $self and add a ‘cleanup’ function which goes and undefines each $headers_io_watcher, thus closing the connection to each client before shutting down. So now I have a hash in $self with all the $headers_io_watcher past and present. when a new connection arrives I add the new $headers_io_watcher into the hash and remove any which are undef – i.e. connection closed. At the end when a cleanup function is called, it goes through this hash and undef’s each value.

Still pointers to AnyEvent tutorials are needed. Thanks for the post, it was most useful for me.

By: Andres

Andres — Tue, 10 Jul 2012 14:38:25 +0000

It does not accept multiple connections when I run it. It closes the current connection and then accepts the new one when another client connects to it.
any ideas? or any pointers to tutorials on AnyEvent?

By: Jared

Jared — Sat, 16 Apr 2011 12:51:49 +0000

Hi Bill,

Thanks for that – should be fixed now.

I’ve amended your comment to what I think you had originally as WordPress would have swallowed thinking it was a tag. Let me know if it isn’t correct.

By: Bill

Bill — Thu, 14 Apr 2011 21:14:18 +0000

Interesting page, thanks for putting it up! I’m looking at AnyEvent and came across your page, and it was helpful in trying some new things out.

There’s a small bug, however, in watch_socket(). The handle is read like so:

while (defined(my $line = )) {

The bareword ‘sock’, as you have it, is undefined.