Till now, we have been successful in creating self-contained reusable components. These components render themselves and handle actions that can be served in isolation, irrespective of where the components are being used.
As we learned earlier in the chapter, events that are raised from the component's template are looked up in the component's action object. These events don't bubble up to the application's controllers or routes.
This all works fine till the components need to inform the rest of the application to take some business decisions. Ember.js framework lets your components translate the component events into meaningful application actions by using the
sendAction method, accessible ...