- From: "Horacio Sanson" <hsanson AT gmail.com>
- To: sctp-discussion AT sctp.de
- Subject: [SCTP-Discussion] SCTP socket API compatibility
- Date: Mon, 16 Jun 2008 14:21:09 +0900
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=cP2OSxavKjuX9Z01DTfYzFYuAlkepMnfj+uk1qjttdAXqfCUptINSBkzbw9PGUe+sk CgsnKrFIpVN3H9/BYAWT4/ctAWAAIfduMjo3HWvvLaoKij18aPi2rA0fS0Gqi7mu53W6 4E36fRSxx1PLw8sK/z52u6VwpQQuDaFJloAKI=
- List-archive: <http://lists.franken.de/pipermail/sctp-discussion>
- List-id: SCTP Discussions <sctp-discussion.sctp.de>
Just wondering how compatible is this sctplib to the current sctp
socket API draft and if this library supports the SCTP reliability
extension.
Seems to me this implementation got stuck at version 1.0.7 and there
seems to be no further development. Is this the last release we will
see?? If so does anyone knows a good SCTP alternative for Windows
platforms??
thanks
Horacio
- [SCTP-Discussion] SCTP socket API compatibility, Horacio Sanson, 06/16/2008
Archive powered by MHonArc 2.6.19+.