[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: LuaSocket 3.0? (was Re: A proposal for faster userdata type checking)
- From: Petite Abeille <petite.abeille@...>
- Date: Fri, 29 Feb 2008 01:28:02 +0100
On Feb 29, 2008, at 1:08 AM, Diego Nehab wrote:
No. If you really need compatibility, there is no reason to
use 3.0. We will continue to support 2.0.x for bugs etc.
The assynchronous APIs present a different programming
paradigm, so it doesn't make sense to be compatible there.
Considering that Lua's threading model is cooperative and that most
library operations are blocking, I don't see much benefit from an
asynchronous socket API in practice. Or at least in the narrow
confines of my current endeavors :)
On the other hand, 3.0 will have a dispatch.lua module that
will be very, very similar to 2.0.x. We will also have a
compatibility layer that will allow for applications using
an API that is very similar to 2.0.x.
At the moment, it is hard to evaluate how close we will get
to the exact old API, though. It should be possible to implement
select() on the new API, but I bet it will be slower than
the current library.
I see... will stick with 2.x for the moment then.
THanks for the insights.