Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Currently Domino clusters do not support the concept of "better" servers for a specific client. As stated in Clustering over a wide area network the user might end up connecting to (and being stuck with) an inferior location and suffer from network penalties.
The solution should support the concept that "better" might change over time (user being in office or deployed in the field; maintenance shutdowns; performance problems ...).
Using Location documents and standalone servers will allow the users to
connect to the "best" Server. Mail delivery on the other hand is tied to
the users home server.
In a failover situation the user will not receive any emails until his
home server becomes available again.
At a remote location the user has to wait until the emails are replicated
from the users home server even when the mails are originating from the
local server.
As far as I can see Panagenda's MarvelClient configuration is more
directed to the configuration of the notes client and does not do much
with the "Mail Server" entry in the public addressbook.
The Notes client is searching for the next available server hosting a replica of the database. Beside the cluster lookup, Notes will also use the catalog server (or Home server) listed in the Location document. If you don't want clients to fail over, consider using two standalone servers rather than a cluster. If you want your clients to connect to the next available server, consider using Panagenda's MarvelClient configuration capabilities. It can configure the client based on its network location.