[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: LuaSocket and IPv6
- From: Matthew Wild <mwild1@...>
- Date: Wed, 24 Feb 2010 20:08:58 +0000
On 24 February 2010 19:42, Sam Roberts <firstname.lastname@example.org> wrote:
> On Wed, Feb 24, 2010 at 11:19 AM, Matthew Wild <email@example.com> wrote:
>> On 24 February 2010 18:52, A.S. Bradbury <firstname.lastname@example.org> wrote:
>>> On 24 February 2010 12:58, Matthew Wild <email@example.com> wrote:
>>>> Does anyone have thoughts on this?
>>>> Further reading:
>>> I just thought I'd add that Steven Barth's Apache-licensed nixio has
>>> IPv6 support.
>> Good to know. Unfortunately LuaSocket is still the more widely used
>> socket library (I know there are others too), and I don't particularly
>> feel like rewriting the socket framework in my server (especially not
>> now I just got it working with libevent).
> You rewrote luasocket's socket.select() to use libevent?
> Or do you just set luasocket's objects non-blocking, retrieve their
> fds, and use a libevent-based call to do your waiting?
We're using LuaEvent, or more accurately a (hopefully temporary)
fork of it.
>> In fact I've looked at nixio before, but can't recall what I didn't
>> like about it, without digging into it again. On the other hand the
>> all-in-one approach is sadly appealing to someone who has spent too
>> long battling against different libraries and their various sore
> I've been tempted by nixio. luasocket attempts to be "high-level" and
> "portable", but its reinventing of the BSD socket API has made it
> difficult for us to use.
I don't mind the fact that it is high-level, it's just annoying when I
need access to options and features it doesn't expose. And of course,