VAMSAS sessions are persistent - this means that they exist independently of any VAMSAS applications that are connected to them.\r
This means that if something goes wrong with a VAMSAS application and it crashes or otherwise fails, the VAMSAS session it is connected to will (hopefully) be unaffected. For instance, if Jalview is killed or crashes whilst it is still connected to a session, that session can be recovered in a new Jalview instance using the <strong>Vamsas→"Existing session"</strong> sub menu.</p>\r
<p>\r
VAMSAS sessions are persistent - this means that they exist independently of any VAMSAS applications that are connected to them.\r
This means that if something goes wrong with a VAMSAS application and it crashes or otherwise fails, the VAMSAS session it is connected to will (hopefully) be unaffected. For instance, if Jalview is killed or crashes whilst it is still connected to a session, that session can be recovered in a new Jalview instance using the <strong>Vamsas→"Existing session"</strong> sub menu.</p>\r
<p>\r