Hi guys!
I have a client web application that uses the Client API to make REST calls
to a REST business layer.
The javax.ws.rs.client.Client docs clearly states that Client objects are
expensive to create and dispose, and only a small number of them should be
created, which makes me think they
, too. Do people use the Apache objects pool library? That's
the only option I've heard of. Are there other mainstream solutions?
Mario
On Oct 27, 2014, at 12:39 PM, Rodrigo Uchôa rodrigo.uc...@gmail.com
wrote:
[...]
How should we implement a pool of Client objects in this scenario
but can I ask though what evidence have you got to believe that?
Perhaps taking a look at the source code would clarify things? (or a
commiter following this thread could verify instead)
On 28 October 2014 01:23, Rodrigo Uchôa rodrigo.uc...@gmail.com wrote:
if Client implementations are thread
only the various flavours of the
target() method seems to be safe. Wouldn't be so sure about the various
provider registration methods though...
Savvas
On 28 October 2014 12:40, Rodrigo Uchôa rodrigo.uc...@gmail.com wrote:
Savvas,
I have no evidence whatsoever. :)
But it seems strange
.
Is this really the case?
Regards!
On Tue, May 26, 2015 at 1:43 PM, Rodrigo Uchôa rodrigo.uc...@gmail.com
wrote:
Thanks a lot, Mike! Exactly what I needed.
On Tue, May 26, 2015 at 6:06 AM, Michael Musgrove mmusg...@redhat.com
wrote:
The narayana transaction manager has a rest service
I have an web application A that occasionally have to insert/update
records that belong to another application, B. To manage this
requirement, application B expose some REST endpoints that application
A will call whenever it needs.
Problem is, we need to make sure that the inserts/updates
I had a similar question in the jersey mailing list. It seems the
specification is open to interpretation. Someone even filled a Jira to this
issue.
http://jersey.576304.n2.nabble.com/Pool-for-javax-ws-rs-client-Client-objects-td7582806.html
On Thu, Sep 17, 2015 at 12:53 PM, Ron Sigal
