[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Idea for an event loop library
- From: Rob Hoelz <rob@...>
- Date: Thu, 10 May 2012 04:23:30 -0400
I can't speak to its effiency, but as far as ease-of-use, the API will
have methods that a "normal" user can understand. For example,
ev:sleep(); it will cause the current handler to sleep for N seconds,
but the user doesn't need to know or care that it's done using
coroutines. They just need to know that as long as they call sleep and
friends, their application will still be able to handle other requests.
I'll probably expose the low-level coroutine stuff at some level for
advanced users/users that wish to extend the library.
On Thu, May 10, 2012 at 09:39:40AM +0200, Dirk Laurie wrote:
> 2012/5/9 Rob Hoelz <firstname.lastname@example.org>:
> > However, that part is just the gravy. The point of doing a whole new
> > library would be to make the entire thing coroutine-based.
> Do you mean the implementation (not seen by the user) will be
> elegant and highly efficient because it is coroutine-based, or that only
> Lua users who understand coroutines will be able to use the library?