commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IO-134) Document thread safety of classes
Date Fri, 05 Dec 2008 19:18:44 GMT

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

Niall Pemberton commented on IO-134:
------------------------------------

I don't think "later" is much use as a status - once something gets resolved then it drops
off the radar and "later" implies its going to be considered/actioned at some point. Without
someone volunteering (and its been over a year) its not going to happen.

Also, while more documentation is always nice-to-have - I don't agree IO needs this.

> Document thread safety of classes
> ---------------------------------
>
>                 Key: IO-134
>                 URL: https://issues.apache.org/jira/browse/IO-134
>             Project: Commons IO
>          Issue Type: Wish
>            Reporter: Sebb
>
> It would be useful to document the thread-safety of all the classes:
> Fully thread-safe (e.g. immutable)
> Thread-safe if particular methods are synchronised
> Thread-safe if specified combinations of methods are synchronised
> Thread-hostile - cannot be used safely from multiple threads

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


Mime
View raw message