NServiceBus: Subscribing to Events with specific property value -

given following event, there way subscribe events have specific property value? example, subscribe events operationtypeid=3.

public interface iserverevent : ievent {     int operationtypeid { get; set; }     string somevalue { get; set; } } 

i using nservicebus 6.0.0.

the use case new operationtype's can created on server need "generic" event structure. i'd ability subscribers receive events operationtype's interested in , not require publisher send events subscribers , make subscriber filter.

i hoping publish side of nservicebus can handle filter reduce number of events published.

what's downside of subscribing event, acting on ones match criteria , ignoring rest?

if in control of publishing side , if events specific value mean business, maybe need break generic event , publish finer grain ones?

as why nservicebus doesn't support content-based routing, maybe this read original author?

tl;dr "because dangerous pattern should avoided"