NETDUMP "standard"

netdump was deliberately designed to be client-heavy. an expansion of the system on the server side should thus be at its most straightforward. the dynamics of extension and scalability of the entire netdump network are absolutely central to the concept. any number of ftp servers can extend the netdump depot at any time. additionally, no server extension is expected of the ftp servers. the initial configuration merely involves setting up of access authorisation and a prescribed directory structure, which can be carried out by the dumpmaster utility within a few minutes. on the other side, the client applications should supply maximum user friendliness to the users. the functional complexity is hidden by the gui. also, the client applications do not require configuration by the users. both the netdump recycle bin and the netdump collector are immediately operational. however, the experienced user has the opportunity of customising numerous features through the popup menu in the systray bar.

the advantages of the client-heavy design do not lie in the extendibility of the netdump capacity alone. the integration of the clients close to the operating system allows functions which would not be possible otherwise. as noted above, the focus is on the human and not the technological aspect of usability. the integration of the clients offers the possibility of providing features which cause a natural user interface where all of the ideas of the concept are implemented 1:1, with no compromises.

automatic sorting of datatrash, extraction of file data, conversions, previews, datastreams, various searches, file system modifications and much more thus serve as a basis isolated from the gui.

NETDUMP 2 ACTIVE (possible future release parallel to standard netdump)

despite the described advantages of the currently only version of netdump there are also disadvantages which may be reason for the development of a second netdump version parallel to the first. firstly, netdump 'standard' currently only runs under windows and secondly it requires the download and installation of client applications from the internet. this problem could be solved by creating 'fat servers'. in this case, all of the services would run on the servers and expanding the system would suddenly become complex and costly. however, the user would no longer be limited to certain operating systems and would no longer be tied to downloads and installations. the client applications would now be replaced by simple scripts, which can be executed simply and rapidly by web browsers. file format conversions and similar services would be carried out by the servers. the great disadvantage of this approach: the servers would be burdened with activity while relieving the client computers. the danger which may arise in this situation should be noted: the sudden increase of data requests to the server may cause considerable delays in the system. furthermore, attention should be directed toward a user interface which is integrated into the conventional browser interface. as of yet, these are problems waiting for creative and unconventional solutions.

a first step toward realising this server-active variant of netdump would be the extensive use of file format conversions. for each file in the netdump network, the user can choose the file format most appropriate for him from a list of available format conversions. the server then prepares the file correspondigly and the user can be certain that the downloaded file will be readable for him. a preliminary list of possible file format conversions can be viewed here: goto> convertable and supported file formats.

last html-update: 03.jul 00 // last content-update: 03.jul 00
copyright (c) Gerhard Schwoiger, 2000 // contact: gerhard@v-a-m-p.com