Defining the Broadcaster and Listener Relationship

John Lindquist
InstructorJohn Lindquist
Share this video with your friends

Social Share Links

Send Tweet
Published 4 years ago
Updated 3 years ago

It's time to set up the core of the pattern we'll be using throughout the entire course. Establishing a contract between functions and rules that we'll follow will allow us to use and define many different functions interchangeably. For many people, "pass a function to a function" is a difficult new concept, but with repetition and using this pattern in many different scenarios, we hope to make it very comfortable so it can be a useful pattern in your JavaScript tool belt.

John Lindquist: [0:00] Throughout this course, you'll hear the words broadcaster and listener in almost every single lesson. I give them these names because listener is just a callback, meaning a function that you pass to something else.

[0:14] Our listeners will take values and do something with those values, usually console.logging them until we start building out UI later on. You can think of a listener as just a plain old function that you can pass to another function.

[0:28] That other function that we'll pass the listener to is a function we'll call broadcaster. This function takes a listener as a callback and then calls that listener in various ways. I could call it three times. I'll pass in the values 1, 2, and 3.

[0:47] Right now, nothing happens in our app until we actually call broadcaster and pass in the listener. Once I hit Save here, you'll see 1, 2, 3. The order is that we invoke broadcaster, which calls this function, with this listener function, which is this function. That listener comes through. We can call it with whatever values we'd like to pass into the listener.

egghead
egghead
~ 14 minutes ago

Member comments are a way for members to communicate, interact, and ask questions about a lesson.

The instructor or someone from the community might respond to your question Here are a few basic guidelines to commenting on egghead.io

Be on-Topic

Comments are for discussing a lesson. If you're having a general issue with the website functionality, please contact us at support@egghead.io.

Avoid meta-discussion

  • This was great!
  • This was horrible!
  • I didn't like this because it didn't match my skill level.
  • +1 It will likely be deleted as spam.

Code Problems?

Should be accompanied by code! Codesandbox or Stackblitz provide a way to share code and discuss it in context

Details and Context

Vague question? Vague answer. Any details and context you can provide will lure more interesting answers!

Markdown supported.
Become a member to join the discussionEnroll Today