

![]() | Start a set with this search |
![]() | Include this search in one of my sets |
![]() | Exclude this search from one of my sets |
![]() | Permalink to these results Paste this link in email or IM: |
| Atom feed for tracking future search results Paste this URL into your reader: |
22 messages in ru.sysoev.nginxRe: Access key module| From | Sent On | Attachments |
|---|---|---|
| Evan Miller | Dec 29, 2007 7:19 pm | |
| Cliff Wells | Dec 30, 2007 12:53 am | |
| Manlio Perillo | Dec 30, 2007 7:41 am | |
| Cliff Wells | Dec 30, 2007 3:47 pm | |
| Grzegorz Nosek | Dec 31, 2007 12:32 am | |
| Manlio Perillo | Dec 31, 2007 3:43 am | |
| Manlio Perillo | Dec 31, 2007 3:55 am | |
| Grzegorz Nosek | Dec 31, 2007 5:31 am | |
| Manlio Perillo | Dec 31, 2007 6:46 am | |
| Evan Miller | Dec 31, 2007 8:00 am | |
| Grzegorz Nosek | Dec 31, 2007 8:07 am | |
| Manlio Perillo | Dec 31, 2007 8:32 am | |
| Manlio Perillo | Dec 31, 2007 8:49 am | |
| Grzegorz Nosek | Dec 31, 2007 9:06 am | |
| Adrian Perez | Dec 31, 2007 9:52 am | |
| Evan Miller | Dec 31, 2007 12:12 pm | |
| Evan Miller | Dec 31, 2007 12:41 pm | |
| Grzegorz Nosek | Dec 31, 2007 1:06 pm | |
| Cliff Wells | Dec 31, 2007 3:34 pm | |
| Manlio Perillo | Jan 1, 2008 9:03 am | |
| Manlio Perillo | Jan 1, 2008 9:07 am | |
| Adrian Perez | Jan 4, 2008 8:13 am |

![]() | Permalink for this message Paste this link in email or IM: |
![]() | Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: Access key module | Actions... |
|---|---|---|
| From: | Manlio Perillo (manl...@public.gmane.org) | |
| Date: | Dec 31, 2007 3:55:00 am | |
| List: | ru.sysoev.nginx | |
Grzegorz Nosek ha scritto:
[...]
BTW, how do you suggest to keep the official repo up to date with contrib modules? Igor's releases I can keep track of, but this won't scale to contrib modules. I can either give the developers push access (which I'd rather not do), or set up a mailing list for sending lkml-style "please pull" requests. Periodic updates maybe?
I think that each external module should be kept separate from nginx "core".
An example is my mod_wsgi module, where I provide support for several nginx version using patches.
[...]
I think that an official repository (with vanilla and all the contrib modules in one tree), with some nice bug tracker (trac indeed would be fine) would help. This could also become a place for collecting development documentation (i.e. internal APIs, ways to do things nginx-style, common coding pitfalls, FAQs etc.) which is too technical to put it on the main wiki.
This would be a great thing, but we need the collaboration of Igor, otherwise I would consider it just a fork of nginx.
The "Guide to Nginx Module Development" is a great document but I think that the community could extend it even further, e.g. I'm currently up to date with nginx's shared memory support (which needs getting used to) and load balancer interface, Manlio with his mod_wsgi could probably write a lot of interesting stuff etc.
Yes, with mod_wsgi I have learned a lot of nginx internals ;-).
Unfortunately I'm not very good at writing documentation. However I can start to write single documentation pages for each of the nginx "public" headers, and some documentation page for nginx "astractions" and main concepts (events, process channels, buffer chains, modules and configuration).
Best regards, Grzegorz Nosek
Regards Manlio Perillo







