diff options
| author | Monty Brandenberg <monty@lindenlab.com> | 2013-09-12 20:15:20 -0400 |
|---|---|---|
| committer | Monty Brandenberg <monty@lindenlab.com> | 2013-09-12 20:15:20 -0400 |
| commit | 99c60b83f15a3c40ecf0e5f144cfc060b37c4cf8 (patch) | |
| tree | 71fd7c3bb326d73255d5a63a3ad1d0d9cc9471e0 /indra/newview/app_settings | |
| parent | 622eae65551df9a4ca6843a6a657777ff5e2140e (diff) | |
SH-4489 New debug/dev settings for control over new mesh behavior
While giving myself a full project code review, found a bug in
the MeshUseGetMesh1 setting. Mostly defaulted to old configuration
but used the GetMesh2 caps which would have been a huge DoS
resource sink. Did some documentation maintenance as well while
I was in there. More for the to-do list, etc.
Diffstat (limited to 'indra/newview/app_settings')
| -rwxr-xr-x | indra/newview/app_settings/settings.xml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/indra/newview/app_settings/settings.xml b/indra/newview/app_settings/settings.xml index 9948f9974a..60fc2d349d 100755 --- a/indra/newview/app_settings/settings.xml +++ b/indra/newview/app_settings/settings.xml @@ -9983,7 +9983,7 @@ <key>MeshUseHttpRetryAfter</key> <map> <key>Comment</key> - <string>If TRUE, use Retry-After response headers when rescheduling a mesh request that fails with an HTTP 503 status.</string> + <string>If TRUE, use Retry-After response headers when rescheduling a mesh request that fails with an HTTP 503 status. Static.</string> <key>Persist</key> <integer>1</integer> <key>Type</key> @@ -9994,7 +9994,7 @@ <key>MeshUseGetMesh1</key> <map> <key>Comment</key> - <string>If TRUE, use the legacy GetMesh capability for mesh download requests.</string> + <string>If TRUE, use the legacy GetMesh capability for mesh download requests. Semi-dynamic (read at region crossings).</string> <key>Persist</key> <integer>1</integer> <key>Type</key> |