-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For a company like nginx, this "reference implementation" is a shame #98
Comments
Good day Thomas. I'm Dave McAllister, in the Nginx open source side of the house. Your issue was forwarded to me. I appreciate the concern and you taking the time to point out this issue. I'm working with the product and engineering side to see if we can get a better resolution. However, I've taken a couple of steps to help clarify this.
Additionally, I am asking the Product/project management team for permission to add a directory for "external project of interest". I cannot make any prediction on whether that will be acceptable davemc |
Thanks a lot for the investigation @schittli. |
Hello
We really really hope that nginx inc. does a very much better job developing the nginx product than what nginx touts as a reference implementation here.
In case you haven't noticed: this implementation is not asynchronous and blocks the server. Software engineers have known solutions to this kind of programming problem for many years!
Therefore it would be at least fair if nginx inc. helps its own its customers:
So it's a shame, too, that a customer has to code an nginx-ldap implementation in his spare time to patch the problems of this implementation.
Thanks a lot, kind regards,
Thomas
The text was updated successfully, but these errors were encountered: