There are two things you need your client to tell your server: the file's name and the file's contents. Part of the contents is knowing when the file ends, so either you have to send a length at the beginning, some kind of EOF marker at the end, or else close the connection at EOF.

A simple protocol would be: 

> SENDFILE <size> name<eol>
< OK
> (file contents, exactly <size> bytes)
< OK
Assuming you have the file name and size in variables already, this could be as simple as: 
print SOCK "SENDFILE $filesize $filename\r\n";
$resp = <SOCK>;
if ($resp !~ /^OK/) { die "Bad response\n" }
while(read(INFILE,$_,8192))
{
  print SOCK;
}
$resp = <SOCK>;
if ($resp !~ /^OK/) { die "Bad response\n" }

[download]

In reply to Re: Copying files using a specific port by sgifford
in thread Copying files using a specific port by rupesh

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.