Notes

Each data source represents a remote (server) or local computer. To use any of the registered data sources a data source instance must be created. The user creates such an instance be opening the data source in the Control window's data source pane. BitKinex also creates new data source instances automatically on demand (e.g. by startup when resuming incomplete requests or when starting a transfer from the File Transfer Dialog). The user has to decide if an existing data source instance will be used for the tasks to be performed or if a new instance should be opened. This technique gives users better control over the application and improves the overall performance. For example when the network connections of a network based (FTP, HTTP) data source are busy (e.g. because there are some transfers running) a new instance (with a new set of connections) allows users to browse the remote server faster. Data source instances can be identified by the number extending the data source name (e.g. "MyDataSource #3").

Mirroring in BitKinex is implemented as an extended version of a simple copy command. Select the source directories you want to mirror and drop/paste them at the destination location. You can use the drag-and-drop while holding the ALT key or the extended version of the copy-and-paste sequence to set the mode of operation to "mirror".

Extended versions of the copy, move and delete commands are used by adding the ALT key to the standard "paste" or "delete" hot keys (typically Ctrl+V+Alt, Del+Alt) or by selecting the appropriate menu item ("Ext. Delete", "Ext Paste"). The dialog which then appears allows users to set the additional parameters of a request (e.g. to schedule the operation to the specified time) and/or to choose some of the special modes of operation (e.g. mirroring).

Custom requests can be created by clicking the "Save as Custom Request" button in the request properties dialog. All parameters (including the optional script) are saved. Custom requests automatically appear in the browse window's "Custom Requests" popup menu. This mechanism allows you to expand the standard built-in functionality by adding new (custom) request types.

Using the edit request on a remote server causes BitKinex to download the selected file(s) to a temporary directory on the local machine. These files will be opened in an associated editor. The user has to resume the request processing as soon as he wishes to upload the changes back to the server. This can be done by clicking on the traffic light symbol in the request pane.

There are two options how to control the transfer mode used by FTP downloads and uploads:

1. Specify the extensions of files which should be transferred in ASCII mode.
   This list can be accessed from the FTP data source properties dialog.
   Use this method to setup the default mechanism BitKinex uses during the copy request processing.
2. Select the desired transfer mode in the browse window menu (Data Source -> Transfer mode).
   Use this method if a certain transfer(s) should use other than default transfer mode.

The context menu available in the detail pane of the browse window can be used to send a custom FTP commands. Currently BitKinex does not perform any checks on the strings specified and it is the user's responsibility to send valid FTP commands to the server (this functionality should be used by experienced users only).

All transfers between two servers are indirect by default (files are downloaded to a temporary folder on the local machine first and then uploaded to the destination folder on the target server). The FTP protocol can build direct data connections between two servers (FXP) which can significantly speed up the file transfers. However, many servers on the Internet do not allow such transfers. The user has to be also aware of any firewall that might make the connection impossible. Direct transfers are started using the extended version of the copy request (please see also the FTP settings for more).

The way that BitKinex displays the date/time values can be adjusted by editing the "bitkinex.ds" configuration file. This file is typically located in the user's private profile directory (e.g. "C:\Documents And Settings\MyName\Application Data\BitKinex"). The custom format specification is stored in the TM_DISP_FORM attribute of the main node. As soon as this variable is set a new item ("Custom format") appears in the list of available date/time formats.

Example:

### Node definition: BitKinex ###
NODE: TYPE = GROUP|DS NAME = BitKinex
SET COMMENT Main group.|Includes all data sources available.
.
.
.
SET TM_DISP_FORM %m/%d/%Y
.
.
.

Such setting causes BitKinex to display the time information ( e.g. in the file list pane ) in the form "month/day of month/year" ( e.g. "10/12/2003" ).

The user can specify any combination of the following format identifiers:

+

%a	Abbreviated weekday name
%A	Full weekday name
%b	Abbreviated month name
%B	Full month name
%c	Date and time representation appropriate for locale
%d	Day of month as decimal number (01 - 31)
%H	Hour in 24-hour format (00 - 23)
%I	Hour in 12-hour format (01 - 12)
%j	Day of year as decimal number (001 - 366)
%m	Month as decimal number (01 - 12)
%M	Minute as decimal number (00 - 59)
%p	The A.M./P.M. indicator for 12-hour clock
%S	Second as decimal number (00 - 59)
%U	Week of year as decimal number, with Sunday as first day of week (00 - 53)
%w	Weekday as decimal number (0 - 6; Sunday is 0)
%W	Week of year as decimal number, with Monday as first day of week (00 - 53)
%x	Date representation for current locale
%X	Time representation for current locale
%y	Year without century, as decimal number (00 - 99)
%Y	Year with century, as decimal number
%z, %Z	Time-zone name or abbreviation; no characters if time zone is unknown
%%	Percent sign

The # flag may prefix any formatting code. In that case, the meaning of the format code is changed as follows:

%#a, %#A, %#b, %#B, %#p, %#X, %#z, %#Z, %#%	# flag is ignored
%#c	Long date and time representation, appropriate for current locale. For example: "Tuesday, March 14, 1995, 12:41:29".
%#x	Long date representation, appropriate to current locale. For example: "Tuesday, March 14, 1995".
%#d, %#H, %#I, %#j, %#m, %#M, %#S, %#U, %#w, %#W, %#y, %#Y	Remove leading zeros (if any).

Please visit the BitKinex home page to get the latest news about the current development. We also appreciate comments and suggestions you might have, as well as any bugs you would kindly report to us. Your opinions play a very important role in the design process and you can help us to significantly improve the quality of this software.