Is HTTP an option? Commands, responses and error messages are already segregated — that's the hard part — so it easily achieve your goal using a small client driving a small CGI script.

Client:

my @files = do { my $list_response = $ua->get("$uri?action=list_files"); if (!$list_response->is_success()) { die(...); } split /\n/, $response->content() }; for my $file (@files) { my $esc_file = uri_escape($file); my $get_response = $ua->get( "$uri?action=get&file=$esc_file", ":content_file" => $file, ); if (!$get_response->is_success()) { unlink($file); warn(...); next; } my $move_response = $ua->post( "$uri?action=move&file=$esc_file", ); if (!$move_response->is_success()) { warn(...); next; } }

In reply to Re: Short example using IPC::Open2 or IPC::Open3 by ikegami
in thread Short example using IPC::Open2 or IPC::Open3 by Limbic~Region

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.