* retry_connect weirdness
@ 2009-12-07 12:08 Helmut Eller
0 siblings, 0 replies; only message in thread
From: Helmut Eller @ 2009-12-07 12:08 UTC (permalink / raw
To: emacs-devel
I have some questions regarding retry_connect in Fmake_network_process.
1. if connect() is interrupted (EINTR) the socket is closed via
emacs_close() and a new socket is created on the next iteration.
Wouldn't it be better to retry with the same socket?
I have a server that accepts exactly one connection, i.e. the server
closes the listening socket after accept(). I have the suspicion that
retrying with a fresh socket leads to problems, unfortunately the
scenario is hard to demonstrate due to timing and interrupts etc.
2. what's the matter with those turn_on_atimers/turn_on_atimers
around connect()? Why are timer interrupts allowed
in other places but not during connect? It's especially odd
since connect() can take so long.
3. why is EISCONN ignored?
4. am I the only who's wondering how anything can work at all with this
#ifdef/#ifndef jungle?
Helmut
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2009-12-07 12:08 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-12-07 12:08 retry_connect weirdness Helmut Eller
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.