tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-2357) Release global session write lock if only immutable attributes are read
Date Thu, 12 Feb 2015 14:35:12 GMT

    [ https://issues.apache.org/jira/browse/TAP5-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318277#comment-14318277

Jochen Kemnade commented on TAP5-2357:

[~hlship], I'd like to hear your opinion on this one.

> Release global session write lock if only immutable attributes are read
> -----------------------------------------------------------------------
>                 Key: TAP5-2357
>                 URL: https://issues.apache.org/jira/browse/TAP5-2357
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Jochen Kemnade
>            Assignee: Howard M. Lewis Ship
>              Labels: patch, performance, test
>         Attachments: 0001-Downgrade-the-global-session-write-lock-to-a-read-lo.patch
> Tapestry 5.4 acquires a write lock on the session when reading attributes. This is to
prevent race conditions if the attribute is mutable and modified from multiple threads.
> If an attribute is immutable, the lock could be downgraded to a read lock.
> The patch adds a MutabilityAnalyzer service that uses a contributable chain of command
to check whether an object is immutable. The session locking code uses that service to downgrade
the write lock if the HTTP handler thread only reads immutable attributes.

This message was sent by Atlassian JIRA

View raw message