Re: Disabling Events

Hi Thorsten,
you have raised a very interesting issue. I have not realized that the 
number of created event objects can ever be a problem. What is the 
use-case when this is problematic? What is the approximated amount of 
data you are dealing with. I think we definitely need to do something 
about it. But first I would like to know and better understand the 
use-cases. Is this currently a blocker for you (i.e. how fast you need 
this to be resolved)?
Martin

Thorsten Sturm wrote:
> Hi Martin,
> 
> I'm not sure if the real problem is more in event distribution or creation. If you use a transaction a vast number of events has to be held before they can be distributed. This can lead to memory problems.
> 
> I would like to see a features, that allows me to supress all those events that will be distributed after the transaction has been finished. Best would be to supress event distribution by type (e.g. if you don't care for the change events but want to receive the transaction end event).
> 
> Do you see any way of doing so?
> 
> Thorsten