https://livekit.io logo
Join Slack
Powered by
# helpdesk
  • w
    yep, just testing some calls at this point. There's some hit/miss on when a call gets rendered on the screen but those issues might be issues in our app
  • w
    I'll keep testing
  • d
    sounds good, keep us posted!
  • w
    In the meantime, would you mind helping me understand what an 
    EngineEvent
    is and how its different from a 
    RoomEvent
    ? I'm particularly interested in the 
    ParticipantUpdate
    event
  • w
    What exactly is an 
    Engine
    ?
  • d
    that's internal
  • d
    the participantUpdate gets translated into participant/track changes on the Room/Participant
  • w
    That makes sense thanks
  • w
    In the event of an abrupt closing of the websocket from the client side, is livekit expected to clear out that participant and emit track unsubscribed events right away to all other clients?
  • d
    it's not intended to be used externally, I'll remove it from the exports to be clear
  • d
    yeah
  • w
    ok I’ve seen some zombie tracks get sent back then
  • d
    you'll also get a participantDisconnected message
  • d
    what do you mean zombie tracks?
  • w
    say there are two users, A and B
  • w
    A is publishing tracks, B is subscribed to those tracks
  • w
    A refreshes the screen and abruptly closes the websocket
  • w
    B refreshes its screen
  • w
    B still receives a 
    RoomEvent.TrackSubscribed
    event from As tracks
  • d
    so it takes a few seconds to detect a disconnect
  • w
    sometimes even after A has disconnected for many seconds the event is still fired when B loads the page and first connects to the socket
  • d
    does it eventually get called?
  • w
    sometimes, other times I need to call back in with A
  • w
    in which case I'd assume because A published new working tracks, the old dead tracks are unimportant and B sees As stream
  • d
    gotcha. yeah we need to better detect this.. refreshes
  • w
    the browser refreshing really just translates to the socket closing
  • w
    without sending a leave message/calling 
    disconnect
  • d
    when refreshes happen, the participant name is kept, while participant_id changes
  • d
    so probably some things to re-align it to ensure it's still the same connection
  • w
    is participant_id randomly generated?
1...789...91Latest