From usocket-devel at common-lisp.net Sun Apr 9 11:21:18 2006 From: usocket-devel at common-lisp.net (usocket) Date: Sun, 09 Apr 2006 11:21:18 -0000 Subject: [usocket-ticket] [usocket] #1: Create API for connection-accepting stream sockets Message-ID: <080.fb52c8bea9dcf22af82801bf311fbbac@common-lisp.net> #1: Create API for connection-accepting stream sockets ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: ehuelsmann Type: task | Status: new Priority: blocker | Milestone: release-0.2 Component: tcp-socket | Version: Keywords: | Patch: 0 ------------------------+--------------------------------------------------- Given the fact that Franz is not able to provide a different socket api (internal or published) other than the one they currently provide in ACL (due to the enormous amount of supported platforms), usocket won't be built directly on top of the BSD socket api as provided by - amongst others - SBCL. This means an api has to be dreamed up which is extensible when making the step to getting/setting socket options. -- Ticket URL: usocket usocket From usocket-devel at common-lisp.net Sun Apr 9 13:18:48 2006 From: usocket-devel at common-lisp.net (usocket) Date: Sun, 09 Apr 2006 13:18:48 -0000 Subject: [usocket-ticket] [usocket] #2: Create/extend API to get/set socket options Message-ID: <080.b2b92285a4d69c1f3a056e3a2a762625@common-lisp.net> #2: Create/extend API to get/set socket options ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: default Type: task | Status: new Priority: blocker | Milestone: release-0.3 Component: tcp-socket | Version: Keywords: | Patch: 0 ------------------------+--------------------------------------------------- This item defines this release. No server side api is complete without the possibility to set / get socket options. -- Ticket URL: usocket usocket From usocket-devel at common-lisp.net Sun Apr 9 19:42:12 2006 From: usocket-devel at common-lisp.net (usocket) Date: Sun, 09 Apr 2006 19:42:12 -0000 Subject: [usocket-ticket] [usocket] #3: Implement shutdown() support Message-ID: <080.969ae75406f7d671d022dcacc0143d2a@common-lisp.net> #3: Implement shutdown() support ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: default Type: defect | Status: new Priority: major | Milestone: release-1.0 Component: tcp-socket | Version: Keywords: | Patch: 0 ------------------------+--------------------------------------------------- Support to asymmetrically close the pipe of a stream socket. This is not a must-have for release 1.0, but is considered a major bonus. -- Ticket URL: usocket usocket From usocket-devel at common-lisp.net Sun Apr 9 19:59:41 2006 From: usocket-devel at common-lisp.net (usocket) Date: Sun, 09 Apr 2006 19:59:41 -0000 Subject: [usocket-ticket] [usocket] #4: Create API for send/recv (out-of-band) transmission for stream sockets Message-ID: <080.3e8cc9876b2aed96ad12dbebe0e846fb@common-lisp.net> #4: Create API for send/recv (out-of-band) transmission for stream sockets ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: default Type: task | Status: new Priority: minor | Milestone: release-0.4 Component: tcp-socket | Version: Keywords: | Patch: 0 ------------------------+--------------------------------------------------- It would be great to have, but this issue needs some investigation w.r.t. level of support on different platforms. -- Ticket URL: usocket usocket