[asterisk-bugs] [Asterisk 0014319]: [patch] describe idlecheck in res_odbc.conf.sample more clear

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14319 
====================================================================== 
Reported By:                klaus3000
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   14319
Category:                   Documentation
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-01-23 01:20 CST
Last Modified:              2009-01-27 12:46 CST
====================================================================== 
Summary:                    [patch] describe idlecheck in res_odbc.conf.sample
more clear
Description: 
Hi!

I did not understand correctly what this parameter does unless reading the
code. I think adding this text will make things more clear.
====================================================================== 

---------------------------------------------------------------------- 
 (0098866) klaus3000 (reporter) - 2009-01-27 12:46
 http://bugs.digium.com/view.php?id=14319#c98866 
---------------------------------------------------------------------- 
Just be sure that both of us know what we are talking about:

+; Note: The reconnection is not done in the background, but is triggered
by
+; a new query. Thus, if you set idlecheck => X, every time you perform a
+; query res_odbc will check how long these connection was idle, and if it
was
+; idle for more than X secondes it will close the current connection and

+; establish a new one even if the current connection is still working.

This is not a developer documentation but a verbose user documentation.

> Additionally, adding information on the way things work 1) does 
> not help most users

But it help some of the user. But we do not care about "some" ???

> 2) gets in the way of most users figuring out what they need to
configure

If users should not configure it - remove it. If you have a parameter then
document it that all users understand it.

> So, in fact, the idlecheck parameter was introduced specifically 
> for your issue, and it did solve it. 

I still do not know what my issue was exactly - but it was solved by
updating to 1.4.23. idlecheck did not solved the issue - it just was an
ugly workaround.

Nevertheless I am tired of contributing and arguing for documentation. If
you think that you are more user than me and understand user's concern
better then close the bug again - I do not have that much idle time. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-27 12:46 klaus3000      Note Added: 0098866                          
======================================================================