You need to keep the handle '$hdl' in scope. For the client, you can just move the declaration to global scope. For the server, you need to put them into some sort of global hash so that there can be multiple of them, and when the connection closes, you can remove the one that closed. Of course, in an object-oriented program you would have the server object maintain the connection set in an attribute, so that when the server goes out of scope it closes all its connections.

A less recommended quick-and-dirty way to keep them alive is to have it make a reference to itself, like $hdl->{self}= $hdl; and then you can have the on_error and on_eof remove that reference and allow it to get freed.

In reply to Re: AnyEvent server/client don't cooperate by NERDVANA
in thread AnyEvent server/client don't cooperate by yuri123

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.