From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Cc: ubuntu@geoffair.info
Subject: [Edbrowse-dev] socket.c and socket.h
Date: Tue, 29 Dec 2015 21:46:11 -0500 [thread overview]
Message-ID: <20151129214611.eklhad@comcast.net> (raw)
Thinking about socket ipc for edbrowse,
I resurrected the old files, which were called tcp.c tcp.h,
but I renamed them to socket in that we will probably add udp capability.
Based on the comments in socket.c, I used these for portable sockets
between unix and windows NT. (How long ago was NT?)
I'm sure it worked at one point but who knows if it still does.
Geoff I'm copying to you because I don't know if you still monitor this mailing list.
Please have a look at these files and let me know what you think
with regard to portability and operation.
There is included a test program built by
cc -DTEST_CONNECT socket.c -o testsock
which is in the test debug section of the makefile, so type
make testsock
Then from two different consoles
testsock l 5432
testsock c localhost 5432
l is for listen and c is for connect.
Type lines into the second and they appear at the first, until EOF.
It still works on Linux, don't know about windows.
Beyond this, Geoff, or whomever, we should add udp functions,
as Adam points out.
Or, if this is just too far off to be useful then we can delete them
and start over, but I hope it is at least a place to start.
Karl Dahlke
next reply other threads:[~2015-12-30 2:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 2:46 Karl Dahlke [this message]
[not found] ` <CA+Pgot+=bbdLr6GUo7++a9LRUGCG9uAHqicMcx97zq8DH-Rvrg@mail.gmail.com>
2015-12-31 14:54 ` Karl Dahlke
2016-01-01 2:10 ` [Edbrowse-dev] telling JS about allowXHR Kevin Carhart
2016-01-01 2:43 ` Karl Dahlke
2016-01-01 4:18 ` Kevin Carhart
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=20151129214611.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=ubuntu@geoffair.info \
/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).