Mailing-List: contact dev-help@mina.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mina.apache.org
Received-SPF: pass (nike.apache.org: domain of elecharny@gmail.com designates
 209.85.218.217 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:reply-to:user-agent:mime-version:to:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        b=eQs7W9QjTmrgotZhKDrhGLR2lrcCyMwrwjf2ploxTAVM1BqRjzA6zOvhE0yoVJ4xDv
         7YivOCVdKaEIbQY/+Bocc/4vVJHD+UxsZtd23r/1m6dKMs8rGgDdNWTeh+UEpYahq+fe
         JWeu7A8svRCjv01ZDXPiQBjzmxdTr0cPDJDdU=
Message-ID: <4B5DC468.4080504@gmail.com>
Date: Mon, 25 Jan 2010 17:18:48 +0100
From: Emmanuel Lecharny <elecharny@gmail.com>
Reply-To: elecharny@apache.org
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: dev@mina.apache.org
Subject: Re: [MINA 3.0] Debugging toolkit
References: <f404ff2d1001190741q18a110e4pddbea20172a1bc7f@mail.gmail.com>
 <11995E42-765C-4A1F-B448-07C8588344A2@toolazydogs.com>
In-Reply-To: <11995E42-765C-4A1F-B448-07C8588344A2@toolazydogs.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Alan D. Cabrera a �crit :
>
> On Jan 19, 2010, at 7:41 AM, Ashish wrote:
>
>> Had picked this form one the discussion threads and added to the MINA
>> 3.0 design page, so that we don't loose this.
>>
>> had some initial thoughts around this, like we can some kind of
>> visualization tool build around MINA, which can help us see/debug
>> the MINA based System. One can view number of IoSession's, IoChain's,
>> configuration etc.
>> It could be build as an Eclipse plugin or a standalone UI talking to
>> MINA code via JMX.
>>
>> I am not sure, but we can see if we can extend ProtoTiger as a
>> debugging/visualization tool.
>>
>> These are just some initial thought, will refine the understanding as
>> we progress further with 3.0 design.
>>
>> Any suggestion?
>
> I wouldn't classify these as debugging toolkit but a management 
> toolkit; very critical.
>
> I was also thinking about the logging discussion that we had earlier 
> and I think that I've come around to the thinking that it's important 
> to provide some kind of logging mechanism who's scope is narrowed to a 
> particular session.  (I'm still not sold on the usefulness of a 
> general logging filter such as the one that we have now).
With JMX, and a decent tool (something like MX4J : 
http://mx4j.sourceforge.net/), providing some graphs should be a piece 
of cake.

Being able to track down one single session is also something that a JMX 
based tool can do. Logs ? That's for post-mortem debugging :/
>
>
> Regards,
> Alan
>  
>  
>


-- 
Regards,
Cordialement,
Emmanuel L�charny
www.nextury.com