tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Burch (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-865) MimeTypes.forName should avoid method-level synchronization
Date Fri, 17 Feb 2012 12:25:59 GMT

    [ 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

        

Mime
View raw message