Hi
The client driver will automatically discover all the locators in the system using the one provided and use any alternate ones available when the first one goes down. In addition this information is shared across all the connections from an application. So as long as the locator mentioned in the first connection is available when it was created, then for all the connections client will automatically failover to other available ones when the mentioned one goes down.
Currently there is no transparent failover for transactions. If the server to which a client connection is attached goes down, then the transaction will fail and be aborted. For non-transactional cases (isolation level NONE in JDBC which is the default in SQLFire), the client will transaparently failover to the next available one and redo the operation. Support for transparent failover for transactions without failing active ones will be added in the 1.1 timeframe.
Load balancing is handled during the connection creation time (or during failover) when a locator is available in the system, so client can query it to find a server having the least load.
