You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chemistry.apache.org by "Florian Müller (JIRA)" <ji...@apache.org> on 2010/03/11 09:54:27 UTC

[jira] Created: (CMIS-155) OpenCMIS provider layer should be thread-safe

OpenCMIS provider layer should be thread-safe
---------------------------------------------

                 Key: CMIS-155
                 URL: https://issues.apache.org/jira/browse/CMIS-155
             Project: Chemistry
          Issue Type: Improvement
          Components: opencmis-provider
            Reporter: Florian Müller
            Assignee: Florian Müller


It is recommended to create only one provider object per user and reuse it whenever possible. In a web application this is usually stored in a HTTP session. Modern web applications are making asynchronous requests to the server. It is likely that a session is used by multiple threads in parallel. Although it would be possible to synchronize the whole provider object, it is more efficient to make the small critical areas within the provider layer thread-safe. This also simplifies the life of web application developers.

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


[jira] Resolved: (CMIS-155) OpenCMIS provider layer should be thread-safe

Posted by "Florian Müller (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CMIS-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Florian Müller resolved CMIS-155.
---------------------------------

    Resolution: Fixed

> OpenCMIS provider layer should be thread-safe
> ---------------------------------------------
>
>                 Key: CMIS-155
>                 URL: https://issues.apache.org/jira/browse/CMIS-155
>             Project: Chemistry
>          Issue Type: Improvement
>          Components: opencmis-provider
>            Reporter: Florian Müller
>            Assignee: Florian Müller
>
> It is recommended to create only one provider object per user and reuse it whenever possible. In a web application this is usually stored in a HTTP session. Modern web applications are making asynchronous requests to the server. It is likely that a session is used by multiple threads in parallel. Although it would be possible to synchronize the whole provider object, it is more efficient to make the small critical areas within the provider layer thread-safe. This also simplifies the life of web application developers.

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