|
Specifications |
|
|
|
Technology |
|
||||
|
Requirements |
|
||||
|
Downloads |
None. |
||||
|
Security Prompts |
None. Users receive no security prompts from the browser when using iNetWord. |
||||
|
HTML Format |
|
||||
|
Interoperability |
Pages can be deployed to any host system. Intra-site links and IMG references are all page-relative so you can move pages to any base URL. |
||||
|
Interoperability |
Import/export and copy/paste operations with modern word processors such as Microsoft Word utilize high-fidelity HTML+CSS and operate with virtually no loss of formatting. |
||||
|
Protocols |
HTTP and |
||||
|
Client-Side |
|
||||
|
Back-End |
File management scripts written in
|
||||
|
Capacity |
iNetWord works well on documents 20 pages or less in length. The lack of automated Table of Contents generation, Index generation, and the round trips the HTML makes to and from the server make it impractical to use iNetWord for lengthy documents. |
||||
|
Scalability |
Introduces no scalability limitations. |
||||
|
Security |
The use of HTTPS and FTPS ensures that all data transmitted to and from the server is secure. |
||||
|
Data Loss |
Automatically saves each user's work every 30 seconds. The potential for data loss in the event of a network outage or computer failure is minimal. |
||||
|
Disconnected |
None at this time. We plan to embed the client system into an HTA framework to provide disconnected operation within the browser. |
||||
|
|
|