[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: [ANN] lucid
- From: Andriy Kornatskyy <andriy.kornatskyy@...>
- Date: Sun, 1 Apr 2018 14:49:37 +0000
I was thinking to prefix packages but will delay that for some time while it is still a playground. Likely current naming will cause collision with lua-http module.
The lua-http module is similar to nginx-lua-module since provides HTTP server capabilities. Lucid toolkit is a higher level library that abstracts HTTP server infrastructure while providing additional capabilities like convenient HTTP handlers, middleware, routing, i18n, validation, etc. There are a number of examples  to give a better idea.
> On Mar 25, 2018, at 1:12 PM, Daurnimator <firstname.lastname@example.org> wrote:
> On 25 March 2018 at 18:29, Andriy Kornatskyy <email@example.com> wrote:
>> This is a development preview of lucid , http API toolkit. It is built on top of lua nginx module .
>>  https://github.com/akornatskyy/lucid
>>  https://github.com/openresty/lua-nginx-module
>> Your feedback is greatly appreciated.
> I noticed you have many modules under different require strings,
> e.g. require "security", require "http", require "core.class", require
> "web", etc.
> To prevent confusion and encourage namespacing, would you consider
> moving them all under a "lucid" prefix?
> So that you have e.g. require "lucid.security.crypto.ticket", require
> "lucid.http", etc.
> Otherwise, I'm curious if you'd like to use parts of lua-http
> (https://github.com/daurnimator/lua-http/) for e.g. your headers data
> structure (see https://daurnimator.github.io/lua-http/0.2/#http.headers)
> You could also use it as a different option for a http server.