You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Nick Burch (Commented) (JIRA)" <ji...@apache.org> on 2012/02/17 13:25:59 UTC
[jira] [Commented] (TIKA-865) MimeTypes.forName should avoid
method-level synchronization
[ https://issues.apache.org/jira/browse/TIKA-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210209#comment-13210209 ]
Nick Burch commented on TIKA-865:
---------------------------------
I've had a go at fixing this in r1245426. It'd be good if someone else could confirm I'm locking on the right object though, as synchronization is easy to get wrong...
> MimeTypes.forName should avoid method-level synchronization
> -----------------------------------------------------------
>
> Key: TIKA-865
> URL: https://issues.apache.org/jira/browse/TIKA-865
> Project: Tika
> Issue Type: Improvement
> Components: mime
> Affects Versions: 1.1
> Reporter: Andrzej Bialecki
>
> MimeTypes.forName can avoid method-level sync, instead it could push down the sync block only if a modification of Map<MediaType,MimeType> types is required. In most cases this should be enough to free the common case (i.e. when a media type is already registered) from synchronization.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira