You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Adam Heath (JIRA)" <ji...@apache.org> on 2007/05/14 17:35:17 UTC

[jira] Created: (VFS-158) Call getLastModifiedTime once per loop in DefaultFileMonitor

Call getLastModifiedTime once per loop in DefaultFileMonitor
------------------------------------------------------------

                 Key: VFS-158
                 URL: https://issues.apache.org/jira/browse/VFS-158
             Project: Commons VFS
          Issue Type: Improvement
    Affects Versions: 1.1
            Reporter: Adam Heath
            Priority: Minor


Don't call getLastModifiedTime multiple times in the loop, as it may change between calls.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


[jira] Commented: (VFS-158) Call getLastModifiedTime once per loop in DefaultFileMonitor

Posted by "Mario Ivankovits (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/VFS-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495746 ] 

Mario Ivankovits commented on VFS-158:
--------------------------------------

In this case I am fine with the successive getLastModifiedTime call ... no problem ... if not wantend, that we use the latest value.

> Call getLastModifiedTime once per loop in DefaultFileMonitor
> ------------------------------------------------------------
>
>                 Key: VFS-158
>                 URL: https://issues.apache.org/jira/browse/VFS-158
>             Project: Commons VFS
>          Issue Type: Improvement
>    Affects Versions: 1.1
>            Reporter: Adam Heath
>            Priority: Minor
>         Attachments: feature_getLastModifiedTime-inner-loop.patch
>
>
> Don't call getLastModifiedTime multiple times in the loop, as it may change between calls.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


[jira] Updated: (VFS-158) Call getLastModifiedTime once per loop in DefaultFileMonitor

Posted by "Adam Heath (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/VFS-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Heath updated VFS-158:
---------------------------

    Attachment: feature_getLastModifiedTime-inner-loop.patch

Against svn 501759.

> Call getLastModifiedTime once per loop in DefaultFileMonitor
> ------------------------------------------------------------
>
>                 Key: VFS-158
>                 URL: https://issues.apache.org/jira/browse/VFS-158
>             Project: Commons VFS
>          Issue Type: Improvement
>    Affects Versions: 1.1
>            Reporter: Adam Heath
>            Priority: Minor
>         Attachments: feature_getLastModifiedTime-inner-loop.patch
>
>
> Don't call getLastModifiedTime multiple times in the loop, as it may change between calls.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org