07-01-2020, 06:11 PM
(07-01-2020, 05:28 PM)kudzu Wrote: You can use some kind of token or to pass back and forth either by cookie or URL. You can even use one of the session IDs and then just store your info for that user in a database and access it from both applications.
For session, just increase the time outs. If you really need to coordinate you can set a flag in the DB for that user an with in each application refresh the sessions that are alive in the other instance of the application.
Thank you very much, this is unchartered territory for me. It is clear how a calling app can pass via URL parameters to a called app, what I don't have clear is how a called app can pass back info (URL or otherwise) to the calling app, such as an "I'm back" signal.
In the sessionID scenario, where user info from calling app is stored in database, I would use sessionID as parameter in URL and called app would access the info and process accordingly, right?
When exiting calling app, just window.close is enough or a WebApplication.Terminate is needed?