주메뉴바로가기 본문바로가기

Developer Tool and API

Innovative Development Environment

For developers, InnoDS 8.0 provides a new developer tool that is specialized to develop file transfer UIs and features on web pages. The developer tool will assist developers to easily find the main cause of the errors and handle them in a short time.

The developer tool is built into InnoDS so that developers do not have to install and run an additional S/W. When InnoDS runs, developers can easily run the developer tool using a key combination.

Analyzes Environmental Information

Although a developer sets the same input value many times, sometimes the input value is not reflected on the web page due to many different causes. Featuring the input value checker, the developer can clearly check whether the input value is applied or not.

Without any additional effort, in order for developers to easily grasp the main information that affects the file transfer UIs and features, the developer tool provides 3 kinds of main information such as 1) input value, 2) a client PC and 3) servers environment information.

Specialized Debugging

1. The debugging feature of the developer tool can check typo errors and incorrect value types so that developers do not have to refer to the manual all the time.

2. Developers can check and monitor the overall flow of all different kinds of events InnoDS is running dependently at a glance. The debugging feature also displays very detailed error information, enabling developers to smoothly develop highly complicated UIs more efficiently.

3. Developers do not have to go through cumbersome processes such as 1) editing the actual code 2) reflecting the code to the servers 3) checking the result on the web page, because with the developer tool, they can check InnoDS API's running status in real time. For example when a developer enters JavaScript code such as “alert(‘hello’);” on the debugging window of the developer tool, they can check the result of the code right away.

Analyzes Return Information from Server

InnoDS is designed to automatically respond to and process various file transfer issues that disturb file exchanges, as a result InnoDS always completes transfers perfectly without any user or developer intervention. However in order to handle the following situations, the debugger of the developer tool provides the error information that is returned from servers.

1. When the transfer cannot be started due to the fact that the developer enters an incorrect server URL during the development process.
2. When files are being transferred without complications and the developer wants to check whether there is an error from server or not.
3. When repetitive transfer errors occur while transferring files.

Analyzes Transfer Speed

The developer tool displays changing transfer speeds through a real time graph. Developers can easily analyze and handle the environmental change issues of clients, servers or networks that affect the file transfer speed.

Various Transfer Policies

1. Transfer Speed Policy

Developers can limit the file upload and download speed per Kbyte so that they can set the same speed for all users or set different speeds (high, normal or low) for different user groups.

2. Resume Transferring Policy

Developers can easily set the resume uploading and downloading policy among the 3 options of 1) Always overwrite 2) Always resume 3) Ask users

3. Limit on Size, Type, Number of Files

Developers can restrict attached files that exceed the designated size or number in order to prohibit users from selecting these files, depending upon your company's service policy. Furthermore, developers can permit or restrict the selection of these designated file types such as gif, jsp, png and etc. in Open Dialog.

4. Restrict Image Size (Width, Height)

When users attach image files, InnoDS can check the width and height of the image file and can permit or restrict attachment of the file. Developers can easily set a minimum or maximum width and height as well as the size range.

5. Restrictions to attaching files By MIME-type

Even though some service policies do not allow for the uploading of some files extensions such as .exe, .php, xls, etc., malicious users can change the file extension easily. In order to fundamentally block these attempts, InnoDS analyzes the MIME type of a file. If developers activate this feature and users attach files, InnoDS will extract the MIME type from the file’s header; analyze it and permit or restrict the attachment of the file.

6. Direct/Stream Download

InnoDS provides two types of download methods

1) Direct download method: If the download files are in the path that user can access with “http://”, users can download file through the actual file path (URL) directly.
2) Stream download method: In order to download file, users connect only a gateway file like download.jsp.
The actual file path will not be exposed and only authenticated users can download files.

7. File Save Path Setting

Generally, the file save path is selected by the user. InnoDS enables developers to set a recommended save path or a prescribed save path according to the purposes of the service. After setting the prescribed save path, when a user clicks the [download] button, the download will start right away without asking the user for the save path.

Situational Upload Events

With InnoDS’s APIs and situational events such as automated attachment and upload, developers can conveniently develop special usage UIs and link with third-party modules and so on.

Situational Download Events

With InnoFD, developers can receive and utilize various information (download URLs, a save path that is selected by a user, total file size, total number of files, each file’s name and size, etc.) and easily develop various download UIs. For example when a user selects files, using the selected download file list, the download can be automatically started.

Allows Attachment by link with Third-party module

As the event before attaching the selected files, detailed information (file path, name and size, etc.) of the selected files can be sent to a third-party’s verification module. According to the return values of the third-party’s module, InnoDS can permit or reject file attachments and display messages to the user.

DRM Auto Applied to Selected Files

As the event before attaching the selected files, detailed information such as the file path and the name of the selected files can also be sent to a third-party’s DRM module. In this process, DRM is applied to these files, the files that are attached by the user will be replaced as DRM-applied files. These will then be automatically uploaded to servers.

Update various Information in the UIs

With the 2 events that occur after files are attached or removed, developers can easily display and update the attachment information such as the entire file size, entire number of files and etc.. This allows developers to freely customize and implement UIs.

Various Upload Function Buttons

Developers can freely implement various transfer buttons such as [Upload], [Download], [Remove the selected file], [Document files browse..], [Folder browse..] and etc. with HTML Tags such as <input type=button..>, <img src..>, <a href..>, <div..> and etc.

Restrictions to Remove Attached File

2 events occur before and after deleting the attached files. The event before deleting the attached files is commonly used so that the user would not be able to delete the required attached files.

Customize Click and Double Click Events

Developers can customize click and double click events with various functions such as download, open, execute a file, as well as, show function menus, etc.

Situational Transfer Status Events

Developers can create appropriate display messages for end users or can alternatively implement messages/processes according to various situational events like: the beginning and end of an up/download, network/server failure or cancelation by user, etc.

Supports User Authentication

InnoDS automatically communicates with the server using the web browser's user authentication information.
Without repeating the authentication process, only authenticated users are able to transfer files in their web business system through InnoDS while the server’s security policy is maintained

Implements Custom POST Header

Developers can implement the POST header and it can be used for various purposes. In order to distinguish the user's files in the server, files sent by the user can be comprised of the same POST header. Also, developers can individually designate POST headers for each file, save them in different paths and it can be utilized for various uses.

Returns Error Messages

As soon as various errors that occur during the development process are received, such as server-side syntax errors and HTTP response errors; InnoDS will classify the errors and display a message to assist the developer so that they can handle the issue with promptness.

Shorter Code, More Features

The latest version of InnoDS improves the inconvenience of writing and editing long codes that were necessary in actions like multiple attachment areas on a page, resuming transfers, modify mode, etc.. Various APIs have also been added and convenience for developers has also been innovatively upgraded.

Integrated Client/Server Module

InnoDS provides the client module with the server module in order to efficiently transfer large files. The high-performance server-side module is optimized for all Java environments and 32/64bit Windows-IIS ASP and .NET environments. It enables upload performance to be improved beyond expectations.

Supports All Server Languages & Environments

InnoDS supports server side script language such as JSP, ASP, .NET, PHP and all kinds of server OSes such as Windows, Linux and Unix. Also, InnoDS can be used right away in various WAS/Web Server environments without any additional server settings. Currently, InnoDS is most commonly used in server environments such as: