Thin Client Usage in Long-term Archivation Environment
Name and surname of author:
LTA, XML, LTAP, PHP, system, thin client, electronic document
DOI (& full text):
This paper focuses on a new approach to the solution of users‘ communication problem with the long-term archive services. In the business, government, or any other environment could be real…more
This paper focuses on a new approach to the solution of users‘ communication problem with the long-term archive services. In the business, government, or any other environment could be real situations, when usage of the original thick client cannot be applied because of its special requirements. On one hand thick client ensures highest possible error free assignment, and on the other hand thin client usage can be a solution in special cases. Its goal from the very begging wasn‘t to replace thick client, but just supplement it in the environments where thick client cannot be used while still makes its main functionalities accessible. Typically in the huge organizations with non-unified company IT policy thin client could be contribution. However usage of thin client has its limitations which will be expressed within the article. Emphasis will be placed on main differences between two previously mentioned solutions in different environments as well as their mutual comparison. Moreover, big difference between thick and thin can be found in the way how and which data are transmitted between server and client along with security admissions which will be revealed likewise. Then functional principles of this brand new solution will be revealed along with roles of users, their permissions, and division into groups, plus their influence on system part. Security related things will be briefly mentioned too along with some drawbacks of the proposed solution. At the end self web interface layout of the long-term archive service server mediator will be explained and briefly described.