title: Advice on using IMvxMessenger vs using a Service based event
body: <p>I am creating 10-20 core services in a large application that need to publish various events.  I have looked at the IMvxMessenger model and I am trying to ascertain the value in using IMvxMessenger events vs events that are published via our application services.</p>
  
  <p>The main advantage I have with the event being published via one of our services is that developers who use the service can quickly determine what events are available.</p>
  
  <p>e.g. myService.ObserveLogonChange() or myService.LogonChangedEvent etc.</p>
  
  <p>When looking at IMvxMessenger it allows you to publish any class in a very generic way – but knowing how to subscribe to these relies heavily on the developers having a deeper understanding of the code base to know which events to listen too.</p>
  
  <p>So my question is, Is there anything that I lose by having the service publish the event vs the IMvxMessenger approach?</p>
  
  <p>Thanks in advance.</p>
  
  <p>Alan.</p>