Hi,
I'm thinking of writing a IOlib backend for USOCKET. There's no doubt that IOlib is a better choice of CL networking library for people whom love (or at lest not hate) loading CFFI, C-based DLLs and lots of third party packages into their CL platforms. And, IOlib's io.multiplex package is also a better way to do "select" on multiple sockets.
In my idea, there will be a new "usocket-iolib.asd" system, which depends on IOlib's networking part, and will load USOCKET core plus a special backend for IOlib. This backend just assume IOlib is a new platform, and use IOlib's networking API to implement all USOCKET API.
Will this idea be helpful for any USOCKET user?
Regards,
Chun Tian (binghe)
On Mon, Oct 4, 2010 at 15:01, Chun Tian binghe.lisp@gmail.com wrote:
I'm thinking of writing a IOlib backend for USOCKET. [...]
Will this idea be helpful for any USOCKET user?
It will not be helpful to me at the moment, but I do like the idea - It would be particularily nice if it would be easily possible to use USOCKET and still use the I/O multiplexing facility of IOlib (i.e. run some USOCKET based libraries and add more file descriptors to the I/O multiplexer without having to resort to threads).
-Hans
It seems to me, that usocket and IOlib are two projects of mostly the same abstraction level, that implement alternative approaches: Lisp-runtime-backed and OS-backed sockets. And it would be better, if the alternatives both remain.
Best, Vsevolod
On Mon, Oct 4, 2010 at 4:07 PM, Hans Hübner hans.huebner@gmail.com wrote:
On Mon, Oct 4, 2010 at 15:01, Chun Tian binghe.lisp@gmail.com wrote:
I'm thinking of writing a IOlib backend for USOCKET. [...]
Will this idea be helpful for any USOCKET user?
It will not be helpful to me at the moment, but I do like the idea - It would be particularily nice if it would be easily possible to use USOCKET and still use the I/O multiplexing facility of IOlib (i.e. run some USOCKET based libraries and add more file descriptors to the I/O multiplexer without having to resort to threads).
-Hans
usocket-devel mailing list usocket-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/usocket-devel
Vsevolod Dyomkin vseloved@gmail.com writes:
It seems to me, that usocket and IOlib are two projects of mostly the same abstraction level, that implement alternative approaches: Lisp-runtime-backed and OS-backed sockets. And it would be better, if the alternatives both remain.
Indeed. However you should consider the integration of libraries written to use these competing libraries.
We had the case with UFFI and CFFI too. There's a UFFI/CFFI compatibility package to allow libraries using the UFFI API to work with CFFI.
-
Chun Tian -
Hans Hübner -
pjb＠informatimago.com -
Vsevolod Dyomkin