On 10/03/2005 08:49 PM, Colm MacCarthaigh wrote: > On Mon, Oct 03, 2005 at 11:40:27AM -0400, Brian Akins wrote: >
[..cut..] > > Looks useful, but file://|/bin/foo would be very non-intuitive for piped I guess you still can use |/bin/foo because file is the default provider. > loggers, balancing the backwards compatibility might need a bit more, I > guess "pipe://" or "cmd://" schemes might make sense also. > 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.: mysql:// for unbuffered mysql backend mysqlb:// for buffered mysql backend file:// for unbuffered file backend fileb:// for buffered file backend Regards Rüdiger
