From: Ron Michael Khu <ronkhu@ntsp.nec.co.jp>
To: muruganandam@softhome.net, linux-c-programming@vger.kernel.org
Subject: Re: problem in sending a message
Date: Sun, 27 Feb 2005 18:07:31 +0800 [thread overview]
Message-ID: <42219BE3.8060609@hq.ntsp.nec.co.jp> (raw)
In-Reply-To: <cvrpo8$h4g$1@sea.gmane.org>
im not sure where ur problem is...
is it with the sending of bytes/data or with the receiving part??
A:
actual size of image file: N bytes
actual bytes sent: M bytes( where M < N)
B:
actual bytes sent: N bytes
actual bytes read: M bytes ( where M < N)
is it scenario A or scenario B?
or a hybrid??
can u send us some of ur code?
Muruganandam wrote:
> dear all,
> when i sending the image file ,it is not exactly same size.it is lower
> than than actual image file.how to send a image file using sockets.i
> expect from u.
>
> thank you,
>
> with regards,
> C.Muruganandam
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
prev parent reply other threads:[~2005-02-27 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 6:57 problem in sending a message Muruganandam
2005-02-27 10:07 ` Ron Michael Khu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42219BE3.8060609@hq.ntsp.nec.co.jp \
--to=ronkhu@ntsp.nec.co.jp \
--cc=linux-c-programming@vger.kernel.org \
--cc=muruganandam@softhome.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).