The infrastructure mandates a schema on the URL of the type https://domain.com/room?roomId=C132
Initialize a new huddle client instance
consthuddle=newHuddleClient(config);
An example config object can be given as
//write this as it is -- used to check for the recorderconstisRecorderBot=localStorage.getItem("bot_password") ==="huddle01";constconfig:HuddleClientConfig= { apiKey:"<API Key>",// API KEY (issued on the dashboard) hostname:"domain.com:4443",// Domain name with 4443 port roomId:"C132",// Room ID peerId:"rick254",// Peer ID (needs to be unique for every peer) displayName:"Rick Sanchez",// Display Name window,// Your browser's window object isBot,// bot flag};
By this step, you should be connected to the Huddle servers.
Setting up event listeners
The emitter that we imported in the 1st step is used to emit events by Huddle about your application. Please refer to the demo app for application references
The various types of events are:
Trigger: on room status changes
Return value: room status of the type string
emitter.on("roomState", (state) => {//do whatever (ideally switch-case between all state types)});
Please refer to the demo app for application references
Different state types:
connecting
waiting_for_admission
connected
failed
disconnected
trying to connect to the room
waiting admission to join room from host in lobby
successfully connected to the room
failure in connection to the room
successfully disconnected from the room
Trigger: an error event on client/server side
Return value: the error object
emitter.on("error", (error) => {//do whatever});
Please refer to the demo app for application references
Trigger: new peer joins the room
Return value: an entire peer object with all the details
emitter.on("addPeer", (peer) => {//do whatever});
Please refer to the demo app for application references
Trigger: you have a new producer producing to the Huddle servers
Return value: an producer object with details like your production media track (eg. camera/mic/screenshare)
emitter.on("addProducer", (producer) => {//do whatever (ideally switch-case between all state types)});
Please refer to the demo app for application references
Different state types:
producer.type:
camera
mic
screenshare
a camera stream producer
a mic stream producer
a screenshare stream producer
Trigger: you have a new consumer consuming from the Huddle servers
Return value: a consumer object with details like your consumption media track (eg. camera/mic/screenshare)
emitter.on("addConsumer", (consumer) => {//do whatever (ideally switch-case between all state types)});
Please refer to the demo app for application references
Different state types:
consumer.type:
camera
mic
screenshare
a camera stream consumer
a mic stream consumer
a screenshare stream consumer
Trigger: one of the existing peers disconnects from the room
Return value: an entire peer object with all the details about the peer(same as the object received on the "add" event)
Please refer to the demo app for application references
Trigger: you have closed the production of your existing producer to the Huddle servers
Return value: a producer object with details like your production media track (eg. camera/mic/screenshare) peer(same as the object received on the "add" event)
emitter.on("removeProducer", (producer) => {//do whatever (ideally switch-case between all state types)});
Please refer to the demo app for application references
Different state types:
producer.type:
camera
mic
screenshare
a camera stream producer
a mic stream producer
a screenshare stream producer
Trigger: you have closed the production of your existing producer to the Huddle servers
Return value: a consumer object with details like your consumption media track (eg. camera/mic/screenshare) peer (same as the object received on the "add" event)
emitter.on("removeConsumer", (consumer) => {//do whatever (ideally switch-case between all state types)});
Please refer to the demo app for application references
Different state types:
consumer.type:
camera
mic
screenshare
a camera stream consumer
a mic stream consumer
a screenshare stream consumer
Trigger: new peer try to join room and waiting admission in lobby
Return value: an entire peers in lobby(waiting room)
Please refer to the demo app for application references
All the data/states received by events need to be maintained by you in your app. Can be achieved using React states/redux or any similar implementations.
Please refer to the demo app where we use local React states to handle these data.