5 Conclusion

O. Hermanns, André Engbrocks
{"title":"5 Conclusion","authors":"O. Hermanns, André Engbrocks","doi":"10.7591/9781501708282-010","DOIUrl":null,"url":null,"abstract":"were made for get_file operations on a disk to memory basis, i.e. the files were requested from the file servers disk and discarded on the receivers side. Thus we where able to neglect the influence of local disk write operations upon the results. This resembles a scenario where a user requests a certain file (e.g. a drawing) for viewing. Since drawings are typically stored as bitmaps (binary) or as graphic language files (text) we examined text and binary transfer modes. The results are satifying, compared with the maximum achievable throughput at TCP level of 1,185,840 bytes/sec. Especially if we think, that the throughput also includes the server disk reading delays. The vast difference of 200 Kbyte/ sec between binary and text modes is due to the extensive processing needed for ASN.1 character encoding/decoding. We described the design and implementation of a distributed file service which is part of a service platform that supports collaborative product development in engineering environments. Furthermore the file service is careful about openess assumption with respect to application systems (e.g. Computer Aided Design Systems). By avoiding architectural extensions to operating systems, it may serve for the a-posteriori integration of existing systems. The file service is based upon the ISO FTAM file transfer protocol and thus usable in heterogeneous computer environments. Name and location transparency are achieved by the integration of a so called CIM manager in the file transfer process. Furthermore the CIM manager supports joint work upon documents (=files) by allowing various degrees of sharing semantics and keeping a design history log. Based upon the FTAM architectural model, every application system may be file server and file service client at the same time. Through this design, the autonomy of the application systems is preserved while the shared files stored in the distributed file system are controlled by the CIM manager. We did not discuss security aspects (which would have been an important issue) since we use the simple, FTAM defined security mechanisms of user identification via passwords. We further described the ISODE based implementation of the file service and discussed its performance on the basis of measurements take at our prototype implementation. It was shown that the usage of FTAM did not result in performance drawbacks, compared with other file transfer protocols, like FTP.","PeriodicalId":355152,"journal":{"name":"Asante Identities","volume":"482 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2019-08-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"2","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Asante Identities","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.7591/9781501708282-010","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 2

Abstract

were made for get_file operations on a disk to memory basis, i.e. the files were requested from the file servers disk and discarded on the receivers side. Thus we where able to neglect the influence of local disk write operations upon the results. This resembles a scenario where a user requests a certain file (e.g. a drawing) for viewing. Since drawings are typically stored as bitmaps (binary) or as graphic language files (text) we examined text and binary transfer modes. The results are satifying, compared with the maximum achievable throughput at TCP level of 1,185,840 bytes/sec. Especially if we think, that the throughput also includes the server disk reading delays. The vast difference of 200 Kbyte/ sec between binary and text modes is due to the extensive processing needed for ASN.1 character encoding/decoding. We described the design and implementation of a distributed file service which is part of a service platform that supports collaborative product development in engineering environments. Furthermore the file service is careful about openess assumption with respect to application systems (e.g. Computer Aided Design Systems). By avoiding architectural extensions to operating systems, it may serve for the a-posteriori integration of existing systems. The file service is based upon the ISO FTAM file transfer protocol and thus usable in heterogeneous computer environments. Name and location transparency are achieved by the integration of a so called CIM manager in the file transfer process. Furthermore the CIM manager supports joint work upon documents (=files) by allowing various degrees of sharing semantics and keeping a design history log. Based upon the FTAM architectural model, every application system may be file server and file service client at the same time. Through this design, the autonomy of the application systems is preserved while the shared files stored in the distributed file system are controlled by the CIM manager. We did not discuss security aspects (which would have been an important issue) since we use the simple, FTAM defined security mechanisms of user identification via passwords. We further described the ISODE based implementation of the file service and discussed its performance on the basis of measurements take at our prototype implementation. It was shown that the usage of FTAM did not result in performance drawbacks, compared with other file transfer protocols, like FTP.
5的结论
基于磁盘到内存的get_file操作,即从文件服务器磁盘请求文件并在接收端丢弃文件。这样我们就可以忽略本地磁盘写操作对结果的影响。这类似于用户请求查看某个文件(例如绘图)的场景。由于图纸通常以位图(二进制)或图形语言文件(文本)的形式存储,我们研究了文本和二进制传输模式。与TCP级别的最大可实现吞吐量1,185,840字节/秒相比,结果令人满意。特别是如果我们认为,吞吐量还包括服务器磁盘读取延迟。二进制和文本模式之间200 Kbyte/秒的巨大差异是由于ASN.1字符编码/解码所需的大量处理。我们描述了分布式文件服务的设计和实现,该服务是支持工程环境中协作产品开发的服务平台的一部分。此外,文件服务对应用系统(例如计算机辅助设计系统)的开放性假设也很谨慎。通过避免对操作系统的体系结构扩展,它可以为现有系统的事后集成服务。文件服务基于ISO FTAM文件传输协议,因此可以在异构计算机环境中使用。名称和位置透明度是通过在文件传输过程中集成所谓的CIM管理器来实现的。此外,CIM管理器通过允许不同程度的共享语义和保留设计历史日志来支持对文档(=文件)的联合工作。基于FTAM架构模型,每个应用系统可以同时是文件服务器和文件服务客户端。通过这种设计,应用程序系统的自主权得以保留,而存储在分布式文件系统中的共享文件则由CIM管理器控制。我们没有讨论安全方面(这是一个重要的问题),因为我们使用了简单的、FTAM定义的通过密码进行用户识别的安全机制。我们进一步描述了基于ISODE的文件服务实现,并在对原型实现进行测量的基础上讨论了其性能。结果表明,与FTP等其他文件传输协议相比,使用FTAM不会导致性能缺陷。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 求助全文
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:604180095
Book学术官方微信