[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [lyo-dev] OSLC CLient thread-safe implementation

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. Additionaly it would also require to dismiss the usage of the Apache Wink client abstraction, since it is not thread-safe, too.


Regards,
    Benjamin

--
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

On 12.09.2014 16:31, Samuel Padgett wrote:
I already posted on the open-services forum and got the hint by Steve
Speicher to ask here for implementation details.
As Steve Speicher already that the OSLC client is not implemented
thread-safe, I would like to know if there are any solution or efforts,
maybe unofficial also, to use the client in a mutli-threaded environment?
Hi, Benjamin. Apache HTTP client has good support for threading, so I don't
think it would be too difficult.  It might be as easy as using
PoolingHttpClientConnectionManager [1] and getting the HTTP client from
HttpClients rather than our client pool. We would need some code like this [2]
to handle self-signed certificates.

[1] http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/impl/conn/PoolingHttpClientConnectionManager.html
[2] http://stackoverflow.com/questions/19517538/ignoring-ssl-certificate-in-apache-httpclient-4-3/19950935#19950935



Attachment: smime.p7s
Description: S/MIME Cryptographic Signature