You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2007/10/25 20:58:50 UTC
[jira] Created: (IO-134) Document thread safety of classes
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.
[jira] Resolved: (IO-134) Document thread safety of classes
Posted by "Niall Pemberton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IO-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Niall Pemberton resolved IO-134.
--------------------------------
Resolution: Won't Fix
Noone has stepped up to do this, so closing as WONT FIX
> 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.
[jira] Reopened: (IO-134) Document thread safety of classes
Posted by "Sebb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IO-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebb reopened IO-134:
---------------------
I don't think WONT FIX is correct; LATER would be more appropriate as the thread safety needs to be documented at some point.
> 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.
[jira] Updated: (IO-134) Document thread safety of classes
Posted by "Niall Pemberton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IO-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Niall Pemberton updated IO-134:
-------------------------------
Fix Version/s: 2.x
Assigning this to 2.x since no-one has done this or submitted any patches
> 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
> Fix For: 2.x
>
>
> 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.
[jira] Commented: (IO-134) Document thread safety of classes
Posted by "Niall Pemberton (JIRA)" <ji...@apache.org>.
[ 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.