# Connection between inMainClient and inMeeting app instances

**URL:** <https://devforum.zoom.us/t/connection-between-inmainclient-and-inmeeting-app-instances/71771>\
**Category:** Zoom Apps\
**Created:** [July 7, 2022, 12:38am UTC](https://devforum.zoom.us/t/connection-between-inmainclient-and-inmeeting-app-instances/71771 "2022-07-07T00:38:35Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![jose.jassojr](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jose.jassojr/32/32818_2.png) [@jose.jassojr](https://devforum.zoom.us/u/jose.jassojr)\
**Post date:** [July 7, 2022, 12:38am UTC](https://devforum.zoom.us/t/connection-between-inmainclient-and-inmeeting-app-instances/71771/1 "2022-07-07T00:38:35Z")

</div>

Are there any connections between an _inMainClient_ and _inMeeting_ app instances? Do they share anything between each other? Cookies? Session? Are they treated like two separate tabs in a web browser being opened? Any clarification is appreciated.

---

<div class="post-metadata">

**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\
**Post date:** [July 9, 2022, 12:04am UTC](https://devforum.zoom.us/t/connection-between-inmainclient-and-inmeeting-app-instances/71771/2 "2022-07-09T00:04:54Z")

</div>

@jose.jassojr Good question!

They are treated as two separate instances but you can communicate between them either using a Socket approach and/or with the Zoom Apps SDK using `connect` and `postMessage`.

More info [here](https://marketplace.zoom.us/docs/zoom-apps/guides/maintaining-state). I hope that helps! 🙂

---

<div class="post-metadata">

**Author:** ![jose.jassojr](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jose.jassojr/32/32818_2.png) [@jose.jassojr](https://devforum.zoom.us/u/jose.jassojr)\
**Post date:** [July 9, 2022, 12:29am UTC](https://devforum.zoom.us/t/connection-between-inmainclient-and-inmeeting-app-instances/71771/3 "2022-07-09T00:29:53Z")

</div>

Hi @MaxM , thank you for responding! For some more context, it seems that if I have both an inMeeting and an inMainClient app open and I close one of them, it affects the other. Not sure exactly why it does but I’ve been able to deduce that that’s whats causing it.

---

<div class="post-metadata">

**Author:** ![jose.jassojr](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jose.jassojr/32/32818_2.png) [@jose.jassojr](https://devforum.zoom.us/u/jose.jassojr)\
**Post date:** [July 11, 2022, 11:44pm UTC](https://devforum.zoom.us/t/connection-between-inmainclient-and-inmeeting-app-instances/71771/4 "2022-07-11T23:44:12Z")

</div>

@MaxM I think what happens is that when I close either one of the instances, it erases the session info for the other instance. Is that expected behavior?

---

<div class="post-metadata">

**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\
**Post date:** [July 15, 2022, 11:09pm UTC](https://devforum.zoom.us/t/connection-between-inmainclient-and-inmeeting-app-instances/71771/5 "2022-07-15T23:09:18Z")

</div>

@jose.jassojr I haven’t seen this in the past so I wouldn’t think that it’s expected but maybe this was a change made to the client. What version of the client and SDK are you using?

---

<div class="post-metadata">

**Author:** ![ycherry543](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ycherry543/32/49664_2.png) [@ycherry543](https://devforum.zoom.us/u/ycherry543)\
**Post date:** [June 22, 2023, 2:23pm UTC](https://devforum.zoom.us/t/connection-between-inmainclient-and-inmeeting-app-instances/71771/6 "2023-06-22T14:23:32Z")

</div>

An “inMainClient” and “inMeeting” app instances, in most cases, are separate entities with their own contexts and functionalities. They usually do not directly share cookies, sessions, or other specific data between each other.

Typically, the “inMainClient” application represents the main client interface or platform, while the “inMeeting” app instance is a component or module within the main client that handles meeting-related functionality.

Although both instances may be open simultaneously, they are often treated as separate entities, similar to opening two tabs in a web browser. Each instance may have its own set of cookies and session data, allowing them to operate independently.

However, it’s important to note that the specific implementation and behavior can vary depending on the application and the platform it is built upon. It’s best to consult the documentation or technical specifications provided by the application’s developers for precise details on how the “inMainClient” and ["](https://alightmotionpromod.com/) inMeeting" instances interact and share data within your particular application. I hope you get it.
