Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Hi.
It would be really great if APPConnection were thread safe, at least for reading.
When my server application starts up, I would like to create an instance of APPContentManager, login, etc, and then get a reference to the default Repository object. My application would then service client requests, each running in a separate Thread which calls Repository.getConnection() to get it's own Connection (APPConnection) for reading from the backend Repository.
A persistent and shared Repository means that each of many service Thread's doesn't require a separate HTTP request to download the CMIS Service Document, and then overhead due to parsing, type management, etc.
From a first glance, the main problem is that the HttpClient instance is shared among all APPContentManager clients, and APPRespository doesn't synchronize calls to loadTypes().