commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IO-470) Using WatchService in Tailer instead of polling
Date Thu, 04 Jun 2015 23:47:39 GMT

    [ https://issues.apache.org/jira/browse/IO-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573831#comment-14573831
] 

Sebb commented on IO-470:
-------------------------

Note that WatcherService [1] may use polling if the underlying native code does not support
file event notification.
Furthermore "... it is not required that changes to files carried out on remote systems be
detected."

Changing to WatcherService may break code that is tailing a remote file, so I think its use
should be optional.

[1] http://docs.oracle.com/javase/7/docs/api/java/nio/file/WatchService.html

> Using WatchService in Tailer instead of polling
> -----------------------------------------------
>
>                 Key: IO-470
>                 URL: https://issues.apache.org/jira/browse/IO-470
>             Project: Commons IO
>          Issue Type: Improvement
>          Components: Utilities
>    Affects Versions: 2.4
>            Reporter: Jeremiah Orr
>              Labels: Java7, Tailer
>             Fix For: 2.6
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Tailer would benefit from using Java 7's WatchService to detect file changes instead
of polling at a set interval. Tailer could respond quicker to changes, and it would save the
system from constant polling. This of course would mean that commons-io would require Java
7.
> I don't know what the future release plans are for commons-io; if there's an upcoming
version that will require Java 7, I'll happily make this change myself.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message