On 2/21/12 1:13 PM, Matthew Swift wrote:
> Hi Ryan,
>
> We've not used these filters for testing, although in hindsight I can
> see how they would have been useful. For me I found them particularly
> useful as examples, illustrating how to use Grizzly, and in addition
> to the other samples that you already have.
>
> To summarize, judging from their size they don't look like they'll
> bloat Grizzly too much, but there's probably no harm in moving them
> out to somewhere else (perhaps a new unit testing support module?).
>
> Although they're not big, the things that irk me are the JMX support
> and the dependency on gmbal. It would be nice if the JMX support was
> optional - I may want it in a server, but I almost certainly don't
> want it in a client.
Would you mind logging an issue to that effect?
>
> Matt
>
>
> On 21 February 2012 18:43, Ryan Lubke <ryan.lubke_at_gmail.com
> <mailto:ryan.lubke_at_gmail.com>> wrote:
>
> Hey Folks,
>
> I'm curious (I hope Matt and Bongjae are paying attention): when
> testing your custom Filter implementations do you use one or more
> of the following Filters from the core framework?
>
> - DelayFilter
> - ChunkingFilter
> - EchoFilter
>
> I ask as we're looking at ways to reduce the core framework jar
> size. If you've found these Filters to be useful in your
> development, I'm more inclined to say that we leave them where
> they are. If no-one really knew about these, then I'd bet it's
> safe to say that we can move them.
>
> -rl
>
>