cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bill Burke <>
Subject Re: More cache in jaxrs impl
Date Fri, 10 May 2013 11:47:23 GMT
Hope you don't mind giving my 2-cents based on Resteasy.

Unless you're doing in-memory mock JAX-RS invocations, I've found that 
any overhead of JAX-RS is pretty much dwarfed by any 
marshalling/unmarshalling of entities i.e. JSON/XML.  I've also found 
that there's a lot of static processing you can do that still fits under 
spec requirements.

On 5/10/2013 5:50 AM, Sergey Beryozkin wrote:
> Hi Romain
> On 10/05/13 10:27, Romain Manni-Bucau wrote:
>> Hi guys
>> Excepted if i didnt get the code right it seems the endpoint
>> resolution is
>> done each time in rs impl.
>> Couldnt it be cached a bit more? (i think to fixed uri which is common
>> for
>> not GET cases). In such a case cxf could skip a bunch of logic no?
>> The idea is to get perf closer to servlets since jaxrs is close to
>> them (i
>> never said it was the same ;)
>> Wdyt?
> I think it is a not a bad idea at all. We can try to experiment with it
> by introducing an optional servlet parameter so that we can always
> resort to the existing tried and tested approach if needed. The only
> thing it can be tricky to do completely right.
> For SOAP endpoints it can be more predicatable, for RS endpoints a bit
> less, as we effectively have a stem match. Please start experimenting if
> you need it fast, I'm all into JAX-RS 2.0 work now with some other
> planned work to do, but can help with/look into it later on too.
> Thanks, Sergey

Bill Burke
JBoss, a division of Red Hat

View raw message