[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-janitors] #1007: socket egg: socket-close should track closed s
From: |
Chicken Trac |
Subject: |
[Chicken-janitors] #1007: socket egg: socket-close should track closed status |
Date: |
Fri, 12 Apr 2013 06:59:39 -0000 |
#1007: socket egg: socket-close should track closed status
------------------------+---------------------------------------------------
Reporter: zbigniew | Owner: zbigniew
Type: defect | Status: new
Priority: minor | Milestone: someday
Component: unknown | Version:
Keywords: socket egg |
------------------------+---------------------------------------------------
We should probably track socket closed status, possibly by setting the
fileno to #f when socket-close is called. This should prevent accidental
reuse of the socket FD when it is reopened by someone else.
It's not clear whether socket-close should stop throwing an error on
double-close, or if this should be done instead in socket-close*. This
would be appropriate behavior to use in a finalizer. But socket-close* is
targeted for (immediate) use after network error.
Also note there are a bunch of direct calls to _close_socket which might
have to be corrected to track the closed state.
--
Ticket URL: <http://bugs.call-cc.org/ticket/1007>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Chicken-janitors] #1007: socket egg: socket-close should track closed status,
Chicken Trac <=