FastSync Mailbox Client User Interface Comparison |
Prepared by Ron Gorman |
Overview
This document describes three different methods by which a client user may connect to a FastSync® Post Office and compares the advantages and disadvantages of each. Of the three methods, one uses CTI Communications proprietary Mailbox Client software package installed on the client computer, the other two use a standard Web browser. One of the two browser methods uses the plain browser (WebClient) "as is" with no enhancements. The other browser method (WebClient+™) uses an ActiveX extension (for Microsoft Internet Explorer browsers) or a Netscape Plug-In (for Netscape browsers), both of which can be downloaded from the Post Office as needed. The former is referred to as the "Web Client" and marketed as the base WebSync configuration, while the latter is referred to as the "Web Client+" version.
Configuration
The Mailbox Client implementation requires no additional software at the Post Office Server side other than the FastSync Post Office application itself.
For either of the browser implementations, however, a FastSync Web Server program must be installed at the host Post Office site and configured to work in conjunction with the existing Post Office. The Web Client browser must be Internet Explorer version 4.0 or higher, or Netscape Navigator 3.0 or higher or compatible. In either case, the browser must be configured to support the JavaScript programming language. The Web Client+ version of the browser must also support ActiveX, while Navigator Browser Plus configurations must support Java and Plug-Ins. It is recommended, but not required, that either browser be configured to support "cookies."
If the FastSync Web Server is installed at the Post Office site, both Mailbox Clients and browser clients can connect to the same Post Office and share data transparently with each other.
General Comparison
Generally speaking, the non-browser, proprietary Mailbox Client implementation is the most powerful and flexible configuration. This implementation involves added overhead, however, in that the Mailbox Client software (about 6MB) must be installed on the client computer and configured to connect properly to the Post Office Server.
Although the browser implementations (Web Browser and Web Browser+) may lack some of the features of the proprietary Mailbox Client implementation, they are generally much easier to configure and maintain. The client computer need only have a compatible browser installed and configured to connect to the Post Office. For pre-existing corporate intranets and extranets, this requirement is normally already met; it is only necessary to create a hyperlink from the corporate web site to the Post Office Server.
As its name implies, the Web Client+ browser version implementation is more powerful and flexible than the plain Web Client browser implementation. However, it requires the browser to be configured to support ActiveX or Java (as described above) and requires download of the appropriate ActiveX control or Java Plug-In before it can be used.
The table below outlines the differences between the three configurations. A detailed description of each feature follows:
|
Feature |
Mailbox Client |
Browser Based WebClient |
Browser Based WebClient+ (Note 2) |
|
Reconstruct broken files |
Yes |
No |
Yes |
|
Monitor file transmission progress |
Yes |
No |
Yes |
|
Interrupt file transmission in progress |
Yes |
No |
Yes |
|
Change password |
Yes |
No |
No |
|
Send multiple files per parcel (Note 1) |
Unlimited |
Up to 10 |
Unlimited |
|
Send multiple parcels per transaction |
Yes |
No |
No |
|
Receive multiple files per parcel |
Yes |
Yes |
Yes |
|
Receive multiple parcels per transaction |
Yes |
No |
Yes |
|
Send parcels to public mailboxes |
Yes |
Yes |
Yes |
|
Retrieve parcels from public mailboxes |
Yes |
Yes |
Yes |
|
Delete parcels from public mailboxes |
Yes |
No |
No |
|
Refuse unwanted parcels |
Yes |
Yes |
Yes |
|
Keep backup copies of retrieved files |
Yes |
No |
Yes |
|
View archives |
Yes |
Yes |
Yes |
|
Schedule file transfers |
Yes |
No |
No |
|
Work offline |
Yes |
No |
No |
|
Run Configuration Advisor |
Yes |
Yes |
Yes |
Notes:
1. Although there is no restriction on the number of files that can be included in a parcel sent by the Mailbox Client or the WebClient+ Client, the total parcel size is limited to 2 Gigabytes.
2. Uses an ActiveX extension.
Reconstructing Broken Files
If the connection between the client and the server is broken during a file upload or download, both the basic Mailbox Client package and WebClient+ implementations can resume the file transfer from the point at which it left off when the connection is re-established. The base WebClient implementation must restart the file transfer from the beginning.
Changing Passwords
Both the Mailbox Client and WebClient+ implementations allow client users to change their own passwords. With the Plain Browser implementation, a clients password can only be changed by the hub administrator.
Deleting Parcels
Only the Mailbox Client implementation allows parcels to be deleted from a mailbox, subject to security restrictions. Browser clients cannot delete parcels from any mailbox under any circumstance.
Sending Multiple Files Per Parcel
All three client implementations allow multiple files to be sent as part of the same parcel. For Mailbox Client and Browser Plus implementations there is no limit to the number of files. Plain Browser implementations are limited to 10 files per parcel.
Sending Multiple Parcels Per Transaction
Both the Mailbox Client and Browser Plus implementations allow the operator to create multiple parcels within an "out-box", then send the parcels with a single mouse click. The Plain Browser implementation only allows the user to create and send one parcel at a time.
Receiving Multiple Files Per Parcel
All three implementations allow an unlimited number of files to be received as part of a single parcel.
Receiving Multiple Parcels Per Transaction
Both the Mailbox Client and Browser Plus implementations allow the operator to select multiple parcels within an "in-box", then retrieve all of them with a single mouse click. With the Plain Browser implementation, the operator must retrieve one parcel at a time.
Scheduling File Transfers
The Mailbox Client includes a command line interface that allows file transfers to be scheduled using an external event scheduler program. Scheduling can be accomplished by using either a third-party event scheduler, or the powerful CTI Communications Event Scheduler application program packaged with each Mailbox Client.
Working Off-line
The Mailbox Client implementation allows the operator to create outbound parcels off-line and to queue both inbound and outbound parcels while off-line for transmission when a connection to the Post Office is established. Neither browser implementation offers this feature.
Accessing Archives
The Mailbox Client implementation offers immediate access to archive information, so that the operator can immediately see what parcels have been transferred in the past. Although the browser implementations also offer access to archived information, this information must be retrieved from the server, which has a delay of several seconds (and longer if the server is busy).
WebClient+ is a trademark of CTI Communications.