How to best setup View Connection Server and Composer to limit single point of failure?

Hello all,

Just had a few quick questions:

1.)  How is everyone limiting the View Connectoin Server to a single point of failure.  All the reading I've done it looks like everyone sets up two connectoin servers and either does DNS round robbin on it, or puts both connection servers behind a load balancer

2.)  What happens if the View Connection server goes offline while users are logged in and actively using desktops?

3.)  How do you protect View Composer from single point of failure.  It looks like most people are installing this on there vCenter server and just leaving it to VMware HA.

4.)  What happens if View Composer goes down and you have active desktop sessions being used by users that are linked clones

5.)  What does the View Connection Server Replication Partner used for?  Is this a new feature of View 6 that creats some form of Cluster for the connection server?

Let me know,

Thanks