From usocket-devel at common-lisp.net Fri Oct 20 15:54:38 2006 From: usocket-devel at common-lisp.net (usocket) Date: Fri, 20 Oct 2006 15:54:38 -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.8f5e3a65086c46eb71375a387b2a87a8@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: Resolution: | Keywords: Patch: 1 | -------------------------+-------------------------------------------------- Changes (by ehuelsmann): * patch: 0 => 1 -- Ticket URL: usocket usocket From usocket-devel at common-lisp.net Sun Oct 22 08:54:52 2006 From: usocket-devel at common-lisp.net (usocket) Date: Sun, 22 Oct 2006 08:54:52 -0000 Subject: [usocket-ticket] #7: Provide :external-format for stream and stream-server type sockets Message-ID: <080.919cdac204e6655695cb55c73bab234c@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: Keywords: | Patch: 0 -------------------------+-------------------------------------------------- From one of my posts on the mailing list: "On IRC, I had some discussions whether it would be enough to just support octet streams, but it looks like not all implementations support octet streams. Definitely not all of them support :external-format for sockets. So, as I mentioned in earlier posts, it might be a good idea to start depending on flexi-streams: this gives us portable external-formats as well as bivalent streams. The latter is important for many TCP/IP protocols: HTTP has a character header, but binary content. Other protocols have that too (8BIT smtp). So, to stay backward compatible, this is what I'd like to do: - If no external-format is given: just return the raw stream returned by the implementation (as we do now) - If an external-format is specified, create a raw stream with 'octet' element-type and wrap the returned stream with a flexi-stream, exposing the flexi-stream to the caller." -- Ticket URL: usocket usocket