Mailing-List: contact user-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Users List" <user@commons.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-Id: <6833798E-F426-4C3D-A742-827CA80BAD86@apache.org>
From: Torsten Curdt <tcurdt@apache.org>
To: "Commons Users List" <user@commons.apache.org>
In-Reply-To: <18800054.post@talk.nabble.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v926)
Subject: Re: JavaFlow: Prevent method from being instrumented
Date: Mon, 4 Aug 2008 00:35:41 +0200
References: <18800054.post@talk.nabble.com>

Hey Peter,

Of course this *could* be added. Not sure it's really worth the effort  
though.
You sure you can't separate your flow better instead?

cheers
--
Torsten

On Aug 3, 2008, at 18:26, Peter Niederwieser wrote:

>
> Hi,
>
> is there a way to prevent a method from being instrumented by  
> JavaFlow? I'm
> asking because most of my methods are not pausable (i.e.
> Continuation.suspend() won't ever be called from inside these  
> methods), yet
> they are still being instrumented. I fear this will have an adverse  
> effect
> on processing time and memory usage (bloated class files and  
> Continuation
> objects). Memory usage is of particular concern because I'm also  
> serializing
> Continuation objects to disk.
>
> Cheers,
> Peter
> -- 
> View this message in context: http://www.nabble.com/JavaFlow%3A-Prevent-method-from-being-instrumented-tp18800054p18800054.html
> Sent from the Commons - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> For additional commands, e-mail: user-help@commons.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org