The client_exited life cycle event seems to be called for all class instances

[MattTheCuber]

We have a class that opens on a new route that the main application calls using template_name. We wanted to attach a listener for when the client disconnects from one of these viewers to cleanup. However, when we initialize multiple of these and connect the client to each, then disconnect from one of the views, the client_exited event is called for each of our class instances.

Snippet:

@TrameApp()
class Viewer:
    def __init__(self, template_name):
        server = get_server(client_type="vue3")
        with VAppLayout(server, template_name=template_name):
            ...

    @life_cycle.client_exited
    def cleanup(self):
        print(id(self)) # This prints multiple different ids

Is there a way to know which window was closed by the client or to only attach the listener to the current class instance?

[jourdain]

Those life_cycle events are bound to a server instance, hence the issue.
But if you want to be individually aware when a given client disconnects from its personal layout, you can do that via a LifeCycle component and trigger a method on the server side with the client/template name.

[jourdain]

Keep thinking out loud here... We could add beforeunload on ClientTriggers.

[MattTheCuber]

I think I finally get it. As you are reusing the same server on which you bind several instance of apps. And you want a specific cleanup method to be called based on which template got closed...

Should we be using a new server for each viewer that the client requests?

[MattTheCuber]

Adding beforeunload to ClientTriggers would be great.

[jourdain]

trame-client>=3.0.1 added a exit= event on which you can bind a method that will be tight to your UI instance.
See this example for reference.

[MattTheCuber]

Awesome, thanks Sebastien! I will try this out Monday.

[MattTheCuber]

This worked great, thanks!