|Re: [lyo-dev] OSLC CLient thread-safe implementation|
-- Benjamin Röhl Phone: +49-391-54456936 pure-systems GmbH Fax: +49-391-54456990 -- pure-systems GmbH Geschäftsführung: Danilo Beuche, Holger Papajewski Sitz der Gesellschaft: Magdeburg Registergericht: Amtsgericht Stendal, HRB 113044
Hey Samuel, I had the PoolingHttpClientConnectionManager already in mind, too. I have only few experience programming with the Apache HttpClient. So this suggestion would generally require to re-implement the "OslcClient.java" from zero.I don't think we'd need to start from scratch, but we can investigate more. It would be a nice feature. Can you open a bug at
We already create a separate RestClient instance for each request, so maybe aAdditionaly it would also require to dismiss the usage of the Apache Wink client abstraction, since it is not thread-safe, too.
non-issue? Many RestClients sharing one thread-safe HttpClient.
Description: S/MIME Cryptographic Signature