Ian Holsman wrote:
so.. lets get brainstorming. Let's see HTTP get the prize for most ideas (and beat those java weanies)
LOL! Ok, in all seriousness, error message localization is -sooo- long overdue, and we have a perpetual problem with apr_status_t extention. The next 2.0 release of apr really needs a 'register error results' for a given set of codes... with a number-of-errors to be set aside, and the appropriate callback to convert codes to error messages (notice the intersection with the localization comment above.)
