From usocket-devel at common-lisp.net Mon Dec 18 22:38:44 2006 From: usocket-devel at common-lisp.net (usocket) Date: Mon, 18 Dec 2006 22:38:44 -0000 Subject: [usocket-ticket] Re: #5: Add compatibility layer for trivial-sockets In-Reply-To: <080.4e3b1133882bf10cd1ce6d057c87fcc6@common-lisp.net> References: <080.4e3b1133882bf10cd1ce6d057c87fcc6@common-lisp.net> Message-ID: <089.e4db2d1d280458af04064a27c6309952@common-lisp.net> #5: Add compatibility layer for trivial-sockets ------------------------------+--------------------------------------------- Reporter: ehuelsmann | Owner: ehuelsmann Type: enhancement | Status: new Priority: critical | Milestone: release-0.1 Component: trivial-usocket | Version: Resolution: | Keywords: Patch: 0 | ------------------------------+--------------------------------------------- Changes (by ehuelsmann): * milestone: release-0.2 => release-0.1 * component: tcp-socket => trivial-usocket * owner: default => ehuelsmann Comment: Moving to its own component, now that I created a separate 'library' for just this functionality. BTW: the library resides in the usocket project repository too. -- Ticket URL: usocket usocket From usocket-devel at common-lisp.net Mon Dec 18 22:40:26 2006 From: usocket-devel at common-lisp.net (usocket) Date: Mon, 18 Dec 2006 22:40:26 -0000 Subject: [usocket-ticket] Re: #1: Create API for connection-accepting stream sockets In-Reply-To: <080.fb52c8bea9dcf22af82801bf311fbbac@common-lisp.net> References: <080.fb52c8bea9dcf22af82801bf311fbbac@common-lisp.net> Message-ID: <089.559ca87cb1e9b01742292dad251802d8@common-lisp.net> #1: Create API for connection-accepting stream sockets -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: ehuelsmann Type: task | Status: new Priority: blocker | Milestone: release-0.3 Component: tcp-socket | Version: Resolution: | Keywords: Patch: 1 | -------------------------+-------------------------------------------------- Changes (by ehuelsmann): * milestone: release-0.2 => release-0.3 Comment: Moving to 0.3, now that 0.2 is out. -- Ticket URL: usocket usocket From usocket-devel at common-lisp.net Mon Dec 18 22:45:00 2006 From: usocket-devel at common-lisp.net (usocket) Date: Mon, 18 Dec 2006 22:45:00 -0000 Subject: [usocket-ticket] Re: #7: Provide :external-format for stream and stream-server type sockets In-Reply-To: <080.919cdac204e6655695cb55c73bab234c@common-lisp.net> References: <080.919cdac204e6655695cb55c73bab234c@common-lisp.net> Message-ID: <089.b657bec52fb6aab16db7b4749d6fb81e@common-lisp.net> #7: Provide :external-format for stream and stream-server type sockets --------------------------+------------------------------------------------- Reporter: ehuelsmann | Owner: default Type: enhancement | Status: new Priority: minor | Milestone: release-0.2 Component: tcp-socket | Version: Resolution: | Keywords: Patch: 0 | --------------------------+------------------------------------------------- Comment (by ehuelsmann): Both Franz and Scieneer object to using flexi-streams to do the job of creating bivalent streams. The current best-known solution would be to: - Create a function which translates a common set of external formats into the implementation specific ones - Fall back to flexi-streams on platforms where streams aren't bivalent and don't support any of the other possibly nice features -- Ticket URL: usocket usocket From usocket-devel at common-lisp.net Mon Dec 18 22:45:39 2006 From: usocket-devel at common-lisp.net (usocket) Date: Mon, 18 Dec 2006 22:45:39 -0000 Subject: [usocket-ticket] Re: #7: Provide :external-format for stream and stream-server type sockets In-Reply-To: <080.919cdac204e6655695cb55c73bab234c@common-lisp.net> References: <080.919cdac204e6655695cb55c73bab234c@common-lisp.net> Message-ID: <089.144c6518f2ab2b62571359155f5faaec@common-lisp.net> #7: Provide :external-format for stream and stream-server type sockets --------------------------+------------------------------------------------- Reporter: ehuelsmann | Owner: default Type: enhancement | Status: new Priority: minor | Milestone: release-0.3 Component: tcp-socket | Version: Resolution: | Keywords: Patch: 0 | --------------------------+------------------------------------------------- Changes (by ehuelsmann): * milestone: release-0.2 => release-0.3 Comment: Move into 0.3 now that 0.2 is out. -- Ticket URL: usocket usocket