users@jax-rs-spec.java.net

[jax-rs-spec users] [jsr339-experts] Re: Re: Re: Re: Re: Re: Re: New to the group - comments on the current draft

From: Sergey Beryozkin <sberyozkin_at_talend.com>
Date: Wed, 21 Dec 2011 11:45:02 +0000

On 21/12/11 03:22, Sastry Malladi wrote:
>
> ------------------------------------------------------------------------
> >> Yes, it would require adding annotations. Without any use of an API,
> I'm not sure this case belongs to the spec. I think this should better
> be handled by implementations or other tools (like profilers).
>
> Well, I understand your position that this may not be addressed in the
> spec. But in reality, any organization that uses JAX-RS to deploy their
> services/resources, would want to monitor and measure these metrics
> automatically, especially in the internet world, and would need a way to
> do that. For example, we are doing this currently by writing a jersey
> response filter and approximating by subtracting MBR and MBW times and
> so on. I beg to differ that this is not a profiler/tooling issue

Can filters handle it as well ? They will have a mutable shared map of
properties on the input/output, so that should do; I don't really like
the idea of going to CDI or similar in order to get the basic feature
supported so I'd also like to see if JAX-RS 2.0 can help

Sergey

>
> Sastry
>
> >> -- Santiago
>
>
>
>