Connected event listener

[onebeyond]

Connected event listener

[cressie176]

In Rascal, the broker is a wrapper for one or more vhosts, and each vhost manages its own connection. The vhosts emit connect events, which are forwarded to the broker, however this might not be useful for two reasons...

1. BrokerAsPromised.create won't yield until all the connections have been established, so you won't have the opportunity to registered handlers until after the events have been emitted (but you could listen for connect events following a disconnection)
2. There's nothing to tell the broker which vhost the events are from.

What did you want to use the connect event for?

[duccio]

Thanks for the reply. I'm interested on "connect event" for logging purpose. Can I assume so that after a try...catch block like this:

try {
  const broker = await rascal.BrokerAsPromised.create(rascal.withDefaultConfig(rascalConfigServer))
  broker.on("error", onRascalBrokerError)
} catch (error) {
  onRascalBrokerError(error)
}

Rascal is connected to all the virtual hosts? So:

try {
  const broker = await rascal.BrokerAsPromised.create(rascal.withDefaultConfig(rascalConfigServer))
  broker.on("error", onRascalBrokerError)
} catch (error) {
  onRascalBrokerError(error)
}

console.log("Rascal connected successful to all the vhosts!")```

[cressie176]

Maybe...

try {
  const broker = await rascal.BrokerAsPromised.create(rascal.withDefaultConfig(rascalConfigServer))
  console.log("Rascal connected successful to all the vhosts!")```
  broker.on("error", onRascalBrokerError)
} catch (error) {
  onRascalBrokerError(error)
}

[duccio]

Yeah, for sure, my mistake. Thanks for confirm that BrokerAsPromised.create won't yield until all the connections have been established.