<strong>VAMSAS Session Persistence</strong><br>\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
+ <strong>A quick Demo</strong><br>\r
+ Jalview can talk to itself through VAMSAS. Simply start two copies of the application, create a new vamsas session in one, and connect to the new session in the other. Then load your data into one of the applications, and use the <strong>Vamsas→"Session Update"</strong> menu entry to try to propagate the data to the other application.\r
+ <br>\r
+ <table>\r
+ <tr><td>Data Sharing Capability</td><td>Jalview Version</td>\r
+ </tr>\r
+ <tr><td>Alignments, sequences and annotation, trees, database references, cDNA/protein mappings.</td><td>2.4</td></tr>\r
+ <tr><td>Mouseover location across linked DNA, protein and structure positions.</td><td>2.4</td></tr>\r
+ <tr><td>Jalview project settings (Multiple views, groups, tree partitions, colouring, window positions)</td><td>2.4.1</td></tr>\r
+ <tr><td>Sequence region and column selections</td><td>2.4.1</td></tr>\r
+ </table> \r
+ \r
<p>\r
- For further details, please check the <a href="http://www.vamsas.ac.uk">VAMSAS website</a>. The VAMSAS framework is implemented as a Java 1.4 Library and its source is will be released under the LGPL license. \r
+ For further details about the VAMSAS framework, please check the <a href="http://www.vamsas.ac.uk">VAMSAS website</a>. The VAMSAS framework is implemented as a Java 1.4 Library and depends on a number of other open source projects. Its source is will be released under the LGPL license. \r
</p>\r
</body>\r
</html>\r