Opened 5 years ago

Closed 5 years ago

#1247 closed defect (fixed)

socket timeout confusion

Reported by: gb Owned by: rme
Priority: normal Milestone:
Component: other Version: trunk
Keywords: Cc:

Description

MAKE-SOCKET accepts timeout keyword arguments (:INPUT-TIMEOUT, :OUTPUT-TIMEOUT, and :CONNECT-TIMEOUT); non-null values of these arguments are supposed to be nonnegative REALs (according to the documentation) specifying time in seconds. (

Lower-level code (PROCESS-INPUT-WAIT, PROCESS-OUPUT-WAIT) takes optional timeout arguments which are required to be integers specifying time in milliseconds.

MAKE-SOCKET seems to just pass its timeout arguments unmodified to the lower-level code. Wackiness ensues (in the formm of type-errors). See ticket:1242.

I don't know whether this bug was newly introduced or if it's been present for a long time.

Change History (2)

comment:1 Changed 5 years ago by rme

  • Owner set to rme

comment:2 Changed 5 years ago by rme

  • Resolution set to fixed
  • Status changed from new to closed

(In [16332]) Check and convert I/O timeouts in init-stream-ioblock.

Also check the connect timeout in make-tcp-socket.

Note that ioblock I/O timeouts are expressed in milliseconds, whereas higher-level I/O timeouts are in (possibly fractional) seconds.

Closes ticket:1247 and ticket:1242.

Note: See TracTickets for help on using tickets.