OK, but again, why? The articles I've sen say it is harder to implement and slower. I might be able to see using it for sockets but I have a hard time seeing what benefit there would be for file appenders.
Ralph > On Apr 27, 2014, at 12:16 AM, Matt Sicker <boa...@gmail.com> wrote: > > The neat feature is non-blocking IO. We could use the Channel API for > non-blocking IO in appenders. > > >> On 26 April 2014 23:35, Ralph Goers <ralph.go...@dslextreme.com> wrote: >> 1. Why would it be a neat feature? >> 2. The FileManager uses NIO to lock the file if it was requested. >> 3. Many of the Appenders use Streams. I happen to like that as it allows >> them to share common code. >> >> Ralph >> >>> On Apr 26, 2014, at 6:48 PM, Matt Sicker <boa...@gmail.com> wrote: >>> >>> I see that the current FileAppender/FileManager classes (and parents) all >>> work via streams. Am I missing something, or are there no appenders using >>> NIO? This could be a neat feature for 2.1. >>> >>> -- >>> Matt Sicker <boa...@gmail.com> > > > > -- > Matt Sicker <boa...@gmail.com>
