Skip to content
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

turning MaxKeepAliveRequests into a variable #703

Merged
merged 3 commits into from
May 1, 2014
Merged

turning MaxKeepAliveRequests into a variable #703

merged 3 commits into from
May 1, 2014

Conversation

attachmentgenie
Copy link
Contributor

For the 1.8 release of Subversion , it is now suggested to increase MaxKeepAliveRequests beyond its usual setting of 100 [1]. To allow the apache module to handle this situation this setting needs to be made into a variable.

[1] https://subversion.apache.org/docs/release-notes/1.8.html#neon-deleted

@igalic
Copy link
Contributor

igalic commented Apr 22, 2014

following our CamelCase to under_score conversion, I think that new setting shold be max_keep_alive_requests, but that sounds… too much.

@attachmentgenie
Copy link
Contributor Author

Perhaps it should even be max_keepalive_requests as KeepAlive and KeepAliveTimeout have turned into keepalive and keepalive_timeout.

maxkeepaliverequests => max_keepalive_requests
@attachmentgenie
Copy link
Contributor Author

updated the variable, to max_keepalive_requests. I also just noticed that #623 also provides the same functionality

@igalic
Copy link
Contributor

igalic commented Apr 23, 2014

Since your patch has docs, and tests and merges, you win ;)

@ghoneycutt
Copy link
Contributor

+1

igalic added a commit that referenced this pull request May 1, 2014
turning MaxKeepAliveRequests into a variable
@igalic igalic merged commit ce04ebe into puppetlabs:master May 1, 2014
@attachmentgenie attachmentgenie deleted the MaxKeepAliveRequests branch May 1, 2014 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants