Rüdiger Plüm wrote:
Makes also sense to me since it seems to me that piped logging does not really play well with other things like spread or mysql. On the other side, what about the buffered logging? Would it make sense to make it possible to turn this on and off with each provider? If yes, we might should have schemes that say e.g.:
It seems to me this would be provider specific.
mysql:// for unbuffered mysql backend mysqlb:// for buffered mysql backend
Probably, a mysql module would want each line individual, rather than a large buffer.
file:// for unbuffered file backend fileb:// for buffered file backend
Or, sticking with the uri methods: file:///some/log/path?buffered or maybe: file://buffered@/some/log/path Interesting comments. -- Brian Akins Lead Systems Engineer CNN Internet Technologies
