If you ensure the code ref doesn't get freed, all you need is a means of serializing and deserializing the code reference. The following should do the trick (including keeping the code ref alive):

sub submit_request {
    my ($code_ref, ...) = @_;
    my $callback_id = "$code_ref";
    $registered{ $callback_id } ||= [ 0, $code_ref ];
    ++$registered{ $callback_id }[0];
    _submit_request($callback_id, @_);
}
[download]

sub on_response {
    my $callback_id = shift;
    my $code_ref = $registered{ $callback_id }[1]
        or croak(...);
    --$registered{ $callback_id }[0]
        or delete( $registered{ $callback_id } );
    $code_ref->(@_);
}
[download]

Assumptions:

• The response is always handled by the process that issued the request.
• There is only one response per request.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.