Connectivity

From DKPLP Doc

(Redirected from Server software interface)
Jump to: navigation, search
The connectivity tab.
Enlarge
The connectivity tab.

The tab named Connectivity contains everything related to interfacing with the server.

Contents

Server url

The server url is the complete url (with http://) all the way to the server software interface. For EQDKP that would be something like http://www.myguild.com/eqdkp/. Exactly what should be entered into this field depends on the server software interface.

Server software interface

The server software interface option describes what server interface the client should be using. The option only affects what should be entered as server url.

Custom
The complete url all the way to the file that provides the interface should be entered.
EQDKP with plugin
The complete url to the base of the EQDKP installation should be entered, for example http://www.myguild.com/eqdkp/.

Connect on startup

If the connect on startup checkbox is checked then you will be presented with a login box every time you start the program. Otherwise you will get a login box whenever you try to perform an action that requires an active connection to the server. Connecting on startup can for instance ensure that you have the most recent member list from the server.

Allowed member ranks

The allowed member ranks are the ranks defined by the server that should be included in the member list. The ranks that are not included will not be downloaded from the server, and hence not included in the member list. The ranks can be viewed and edited by clicking on the View button, it requires an active connection to the server. This can be useful in for instance EQDKP to ignore certain ranks while parsing.

Download member list on connect

Checking the download member list on connect checkbox ensures that the latest copy of the server's member list is downloaded to the local DKPLP client when the connection to the server is established. (either on startup or via manual operation) This overwrites the local copy file: any local changes made that weren't uploaded to the server will be lost.

Download completions on connect

Checking the download completions on connect checkbox will make the program automatically download all completions from the server whenever a connection is established. It works just as if one would download the completions via the menu whenever one connects to the server.

Download member aliases on connect

Checking the download member aliases on connect checkbox will make the program automatically download all member aliases from the server whenever the client connects to the server. It works just as if one would download the member aliases via the menu every time one connects to the server.

Upload added members on exit

Checking the upload added members on exit checkbox makes the client perform a last synchronisation with the server when exiting the program. This ensures that any members added to the local member list (through parsing a raid log) are sent to the server to be stored there.

Upload completions on exit

Checking the upload completions on exit checkbox will make the program automatically upload all of its completions to the server whenever the program closes (but only if there is an established connection). It works just as if one uploads the completions via the menu just before one exits the program. This option should be combined with the download completions on connect option, otherwise one might accidentally upload a database that is almost empty, which would replace the server's database and risk hence losing important completions. If the two options are combined then there is never such a risk because the client's database will then always contain at least everything that the server already has.

Upload member aliases on exit

Checking the upload member aliases on exit checkbox makes the program upload all of its member aliases to the server when one closes the program, but only if one is connected to the server. This option should be used with care as any memeber aliases uploaded to the server overwrites any previous uploads, hence one could accidentally ruin the server's version if one does not keep aliases up to date. For that reason it can be good to combine this option with the download member aliases on connect option.

Personal tools