We have an application that talks to remote rest-api's, using resteasy
client framework.
Our code creates a new proxy for each call, and these calls run on new
threads always (we don't cache our client proxies, and the threads are
from a threadpool that is created and shutdown afterward).

We suffer a 5-seconds overhead for each call that actually returns
something (non-void) (using jackson json).

I suppose there's some heavy-weight initialisation going on over and
over. In particular, jackson-docs suggest that we should reuse the
ObjectMapper.

The ProxyFactory.create(...) variations have no javadoc, so i'm
wondering how to configure my client-proxy with some shared
ObjectMapper.

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Resteasy-users mailing list
Resteasy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/resteasy-users

Reply via email to