On Tue, 2006-04-11 at 12:10, Zsolt wrote: > Trygve, > > Are you sure? In this case maven-scm is not an option for us. After spending > some days on maven-scm and implementing ScmProvider.listTask I really like > this API and even plan to add CM-Synergy support, but we are going to use > this API from servlets, thus it must be thread safe. You might know > javaforge.com that is based on our software with hundreds of projects and > thousands of users. Serializing the request is just not acceptable for us > (for the users) because it is very probably that more than one user want to > browse repositories.
If something isn't thread safe just means that you'll have to use more instances of the thing in question. But, if this is something that's really important it wouldn't be hard to ensure (and keep) the core thread safe, and if the providers are used on a per lookup-basis you should be home safe. For all I know the core is practically thread safe already. I think the solution I've outlined above is the easiest solution (keeping the core thread safe, and just instantiate the providers per usage. The biggest issue with this is that the user of the provider will have to return/dispose the instance once it's done with it. -- Trygve
