pmthiagu
Dear All,
Can anyone help out,
How to handle the browser instance closing event in LS java adapter?
Thanks in advance
Regards,
Raja
Dario Crivelli
Do you refer to a browser instance which runs a single pushpage while other pushpages remain alive within other browser instances?
Or does your application consist of only one pushpage and do you refer to the browser instance which runs this only page?
As a general rule, if there is an active session and a page gets closed, the Server will be eventually notified, though with a possible delay;
on the other hand, if the Engine were disconnected at the time the page were closed, there would be no way for the Server to be notified.
We can add more details once your specific use case is identified.
pmthiagu
Dear DarioCrivelli,
Thanks for the reply
"As a general rule, if there is an active session and a page gets closed, the Server will be eventually notified, though with a possible delay;"
Can you please, give the details of Server notification (ie, function name etc) to handle the page closing event.
Thanks and regards,
Thiagarajan
Dario Crivelli
For what concerns my first question, I assume that you are in the simplest case,
that is: your application consists of just one pushpage (which includes its own Engine) and you close the browser, so the whole application gets closed.
This causes the session to be closed, so that the Server can notify the Metadata Adapter through the notifySessionClose callback.
As said, the Server may need some time to understand that the client has detached and, even then, it may wait for some time before sending the notification.
Note, however, that notifySessionClose is invoked upon session closure for any reason.
There is no information about the cause.
