From: Volker Kokula <kokula@informatik.uni-wuerzburg.de>
To: ajhwb@knac.com
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Socket programming
Date: Sun, 22 Mar 2009 16:04:08 +0100 [thread overview]
Message-ID: <49C65368.3080106@informatik.uni-wuerzburg.de> (raw)
In-Reply-To: <20090322070853.1C31EAD6@resin17.mta.everyone.net>
Hi,
yes that what i meant with unportable :-) I would recommend you to read
,,Beej's Guide to Network Programming'' a imo really good ebook about
network programming using sockets
Volker
[1] http://beej.us/guide/bgnet/
next prev parent reply other threads:[~2009-03-22 15:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 14:08 Socket programming Ardhan Madras
2009-03-22 15:04 ` Volker Kokula [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-23 15:03 Ardhan Madras
2009-03-22 15:47 Ardhan Madras
2009-03-22 13:31 Ardhan Madras
2009-03-22 13:41 ` Volker Kokula
2009-03-22 15:24 ` Canaan Kao
2009-03-26 21:42 ` Anil Vishnoi
2009-03-22 12:42 Ardhan Madras
2009-03-22 13:00 ` Canaan Kao
2009-03-22 18:39 ` Jon Mayo
2009-03-26 21:58 ` Anil Vishnoi
2009-03-23 9:18 ` Glynn Clements
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=49C65368.3080106@informatik.uni-wuerzburg.de \
--to=kokula@informatik.uni-wuerzburg.de \
--cc=ajhwb@knac.com \
--cc=linux-c-programming@vger.kernel.org \
/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).