Re: Proposal: error codes

2011-11-30 Thread Stefan Fritsch
On Wednesday 30 November 2011, Tim Bannister wrote: > On 27 Nov 2011, at 17:14, Stefan Fritsch wrote: > > Yes, that would be a good idea and I agree with Daniel that we > > should use a distinct prefix or format. We currently have around > > 2700 calls to *_log_?error in trunk, so a 4-digit number

Re: Proposal: error codes

2011-11-30 Thread Tim Bannister
On 27 Nov 2011, at 17:14, Stefan Fritsch wrote: > Yes, that would be a good idea and I agree with Daniel that we should use a > distinct prefix or format. We currently have around 2700 calls to > *_log_?error in trunk, so a 4-digit number should be ok. Together with for > example AH as prefix f

Re: Proposal: error codes

2011-11-29 Thread Stefan Fritsch
On Tuesday 29 November 2011, William A. Rowe Jr. wrote: > On 11/27/2011 8:34 AM, Rich Bowen wrote: > > At Apachecon several of us were discussing how error messages > > could be made more helpful without making them paragraphs. Two > > suggestions were made - adding a URL to the message or adding a

Re: Proposal: error codes

2011-11-29 Thread William A. Rowe Jr.
On 11/27/2011 8:34 AM, Rich Bowen wrote: At Apachecon several of us were discussing how error messages could be made more helpful without making them paragraphs. Two suggestions were made - adding a URL to the message or adding a number/code to each error that would then be looked up for more

Re: Proposal: error codes

2011-11-28 Thread Mikhail T.
On 27.11.2011 12:14, Stefan Fritsch wrote: Yes, that would be a good idea and I agree with Daniel that we should use a distinct prefix or format. We currently have around 2700 calls to *_log_?error in trunk, so a 4-digit number should be ok. Together with for example AH as prefix for "Apache HTTP

Re: Proposal: error codes

2011-11-28 Thread Guenter Knauf
Am 27.11.2011 18:14, schrieb Stefan Fritsch: Yes, that would be a good idea and I agree with Daniel that we should use a distinct prefix or format. We currently have around 2700 calls to *_log_?error in trunk, so a 4-digit number should be ok. Together with for example AH as prefix for "Apache HT

Re: Proposal: error codes

2011-11-27 Thread Rich Bowen
On Nov 27, 2011, at 12:58, Rich Bowen wrote: > > Thanks for the suggestion of the odd format. That seems very reasonable. Clearly I need to stop writing email on my phone. The CODE format.

Re: Proposal: error codes

2011-11-27 Thread Rich Bowen
On Nov 27, 2011, at 12:14, Stefan Fritsch wrote: > Yes, that would be a good idea and I agree with Daniel that we should > use a distinct prefix or format. We currently have around 2700 calls > to *_log_?error in trunk, so a 4-digit number should be ok. Together > with for example AH as prefi

Re: Proposal: error codes

2011-11-27 Thread Stefan Fritsch
On Sunday 27 November 2011, Rich Bowen wrote: > At Apachecon several of us were discussing how error messages could > be made more helpful without making them paragraphs. Two > suggestions were made - adding a URL to the message or adding a > number/code to each error that would then be looked up f

Re: Proposal: error codes

2011-11-27 Thread Daniel Ruggeri
On 11/27/2011 8:34 AM, Rich Bowen wrote: > At Apachecon several of us were discussing how error messages could be made > more helpful without making them paragraphs. Two suggestions were made - > adding a URL to the message or adding a number/code to each error that would > then be looked up for

Proposal: error codes

2011-11-27 Thread Rich Bowen
At Apachecon several of us were discussing how error messages could be made more helpful without making them paragraphs. Two suggestions were made - adding a URL to the message or adding a number/code to each error that would then be looked up for more information. Any thoughts on 1) the wisdom