Casual Resource Sharing with Shared Virtual Folders

Total Page:16

File Type:pdf, Size:1020Kb

Casual Resource Sharing with Shared Virtual Folders MASTER THESIS IN COMPUTER SCIENCE Casual Resource Sharing with Shared Virtual Folders Siri Birgitte Uldal June 15th, 2007 FACULTY OF SCIENCE Department of Computer Science University of Tromsø, N-9037 Tromsø Casual Resource Sharing with Shared Virtual Folders Siri Birgitte Uldal June 15th, 2007 ___________________ University of Tromsø 2007 Abstract Proliferation of wireless networks has been a major trigger behind increased mobility of computing devices. Along with increased mobility come requests for ad-hoc exchange of resources between computing devices as an extension of humans interacting. We termed it casual resource sharing where resources in this thesis have been narrowed down to files only. We have named our casual resource sharing model for shared virtual folders (SVF). SVFs can be looked upon as a common repository much in the same way as the tuplespace model. The SVF members perceive the repository similarly to a common file directory on a server, while in reality all participating devices stores their own contribution of files. All types of files could be added to the repository and shared. To become a SVF member one needs to be invited by another member or initiate a SVF oneself. All members are free to withdraw their SVF membership whenever they wish. They are also free to log on to the SVF and log out as they please. The SVF cease to exist when the last member has drawn his membership. The SVF implements a simple versioning detection system to alert members when a file has been modified by another member. Feasibility of the model is demonstrated in a prototype implementation based on Java and the JXTA middleware, a peer-to-peer (P2P) infrastructure middleware supporting the Internet protocol. The implementation functions with any underlying network supporting the IP protocol, both LAN or WAN. The interacting devices could be running on any operating system. The SVF itself is created with focus on simplicity and requires no more than software installation before use. The model and implementation is discussed and contrasted with other existing approaches to casual resource sharing. Keywords: Peer-to-peer, JXTA, ad-hoc i ii Preface The master thesis was carried out during 10 ½ month in 2006 and 2007 and is a collaboration project between the Department of computer science at the University of Tromsø and Norut IT. The master thesis started out as a supplement to Njål Borch’s PhD thesis at Norut IT which focused on socialized ad-hoc networks based on peer-to-peer technologies. I would like to thank my advisors Randi Karlsen at the Department of computer science, University of Tromsø together with Njål Borch for their help and efforts through the process of finishing my thesis. I am also grateful to the Norwegian Polar Institute, especially head of Environmental Data Section Stein Tronstad, for allowing me to finish my master thesis. Also thank to the people at Norut IT for allowing me to stay there during work with the thesis. Finally I would like to thank friends and family for their support and bearing with my absence. iii iv Table of contents ABSTRACT...................................................................................................................................................I PREFACE...................................................................................................................................................III TABLE OF CONTENTS.............................................................................................................................V 1. INTRODUCTION................................................................................................................................1 1.1 PROBLEM DESCRIPTION .............................................................................................................. 1 1.2 GOAL AND OBJECTIVES ............................................................................................................... 2 1.3 LIMITATIONS AND ASSUMPTIONS ................................................................................................. 3 1.4 METHOD ...................................................................................................................................... 4 1.5 RESEARCH CONTRIBUTION.......................................................................................................... 5 1.6 OUTLINE ...................................................................................................................................... 5 2 BACKGROUND ................................................................................................................................. 7 2.1 PEER-TO-PEER NETWORKS......................................................................................................... 7 2.1.1 Definition of a peer-to-peer network............................................................................. 8 2.1.2 An overview of P2P networks......................................................................................... 9 2.1.3 Decentralized versus centralized P2P networks ..................................................... 13 2.2 RESOURCE SHARING CONCEPTS .............................................................................................. 14 2.2.1 Remote procedure call (RPC)....................................................................................... 15 2.2.2 Message oriented middleware (MOM) ........................................................................ 16 2.2.3 The publish-subscribe model....................................................................................... 17 2.2.4 Tuple spaces..................................................................................................................... 19 2.3 PROPERTIES OF RESOURCE SHARING MODELS ........................................................................ 22 2.3.1 Interruption handling during data transfer ............................................................... 23 2.3.2 Data push versus pull..................................................................................................... 26 2.3.3 Configuration.................................................................................................................... 26 2.3.4 Incentive mechanisms and accountability................................................................ 27 2.3.5 Persistence and search guarantees ........................................................................... 29 2.4 VERSIONING DETECTION AND CONTROL ................................................................................... 31 2.4.1 Versioning models .......................................................................................................... 32 2.4.2 Versioning detection....................................................................................................... 33 v 2.4.3 Software configuration management (SCM) ............................................................ 34 2.5 MIDDLEWARE FOR P2P NETWORKS ......................................................................................... 37 2.5.1 Why middleware............................................................................................................... 37 2.5.2 Types of middleware....................................................................................................... 38 2.5.3 Characteristics of decentralized P2P middleware .................................................. 40 2.5.4 Bonjour............................................................................................................................... 42 2.5.5 Universal Plug and Play (UPnP)................................................................................... 44 2.5.6 JXTA.................................................................................................................................... 48 2.5.7 The Socialized.Net........................................................................................................... 51 2.6 RELATED WORKS....................................................................................................................... 53 2.6.1 Bluetooth/OBEX/FTP ...................................................................................................... 54 2.6.2 Microsoft Shared Folders/SAMBA .............................................................................. 54 2.6.3 Microsoft Office Groove................................................................................................. 55 2.6.4 iFolder................................................................................................................................. 56 2.6.5 Google Docs & Spreadsheets ...................................................................................... 57 2.6.6 myJXTA .............................................................................................................................. 58 2.6.7 GRAM.................................................................................................................................. 60 2.6.8 Gnutella .............................................................................................................................. 61 3 CASUAL RESOURCE SHARING WITH SHARED VIRTUAL FOLDERS............................. 65 3.1 SCENARIOS................................................................................................................................65 3.2 CASUAL RESOURCE SHARING ..................................................................................................
Recommended publications
  • Uila Supported Apps
    Uila Supported Applications and Protocols updated Oct 2020 Application/Protocol Name Full Description 01net.com 01net website, a French high-tech news site. 050 plus is a Japanese embedded smartphone application dedicated to 050 plus audio-conferencing. 0zz0.com 0zz0 is an online solution to store, send and share files 10050.net China Railcom group web portal. This protocol plug-in classifies the http traffic to the host 10086.cn. It also 10086.cn classifies the ssl traffic to the Common Name 10086.cn. 104.com Web site dedicated to job research. 1111.com.tw Website dedicated to job research in Taiwan. 114la.com Chinese web portal operated by YLMF Computer Technology Co. Chinese cloud storing system of the 115 website. It is operated by YLMF 115.com Computer Technology Co. 118114.cn Chinese booking and reservation portal. 11st.co.kr Korean shopping website 11st. It is operated by SK Planet Co. 1337x.org Bittorrent tracker search engine 139mail 139mail is a chinese webmail powered by China Mobile. 15min.lt Lithuanian news portal Chinese web portal 163. It is operated by NetEase, a company which 163.com pioneered the development of Internet in China. 17173.com Website distributing Chinese games. 17u.com Chinese online travel booking website. 20 minutes is a free, daily newspaper available in France, Spain and 20minutes Switzerland. This plugin classifies websites. 24h.com.vn Vietnamese news portal 24ora.com Aruban news portal 24sata.hr Croatian news portal 24SevenOffice 24SevenOffice is a web-based Enterprise resource planning (ERP) systems. 24ur.com Slovenian news portal 2ch.net Japanese adult videos web site 2Shared 2shared is an online space for sharing and storage.
    [Show full text]
  • OES 2 SP3: Novell CIFS for Linux Administration Guide 9.2.1 Mapping Drives from a Windows 2000 Or XP Client
    www.novell.com/documentation Novell CIFS Administration Guide Open Enterprise Server 2 SP3 May 03, 2013 Legal Notices Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Service Web page (http://www.novell.com/info/exports/) for more information on exporting Novell software.
    [Show full text]
  • Shared Resource Matrix Methodology: an Approach to Identifying Storage and Timing Channels
    Shared Resource Matrix Methodology: An Approach to Identifying Storage and Timing Channels RICHARD A. KEMMERER University of California, Santa Barbara Recognizing and dealing with storage and timing channels when performing the security analysis of a computer system is an elusive task. Methods for discovering and dealing with these channels have mostly been informal, and formal methods have been restricted to a particular specification language. A methodology for discovering storage and timing channels that can be used through all phases of the software life cycle to increase confidence that all channels have been identified is presented. The methodology is presented and applied to an example system having three different descriptions: English, formal specification, and high-order language implementation. Categories and Subject Descriptors: C.2.0 [Computer-Communication Networks]: General--se- curity and protection; D.4.6 ]Operating Systems]: Security and Protection--information flow controls General Terms: Security Additional Key Words and Phrases: Protection, confinement, flow analysis, covert channels, storage channels, timing channels, validation 1. INTRODUCTION When performing a security analysis of a system, both overt and covert channels of the system must be considered. Overt channels use the system's protected data objects to transfer information. That is, one subject writes into a data object and another subject reads from the object. Subjects in this context are not only active users, but are also processes and procedures acting on behalf of the user. The channels, such as buffers, files, and I/O devices, are overt because the entity used to hold the information is a data object; that is, it is an object that is normally viewed as a data container.
    [Show full text]
  • Shared Resource
    Shared resource In computing, a shared resource, or network share, is a computer resource made available from one host to other hosts on a computer network.[1][2] It is a device or piece of information on a computer that can be remotely accessed from another computer transparently as if it were a resource in the local machine. Network sharing is made possible by inter-process communication over the network.[2][3] Some examples of shareable resources are computer programs, data, storage devices, and printers. E.g. shared file access (also known as disk sharing and folder sharing), shared printer access, shared scanner access, etc. The shared resource is called a shared disk, shared folder or shared document The term file sharing traditionally means shared file access, especially in the context of operating systems and LAN and Intranet services, for example in Microsoft Windows documentation.[4] Though, as BitTorrent and similar applications became available in the early 2000s, the term file sharing increasingly has become associated with peer-to-peer file sharing over the Internet. Contents Common file systems and protocols Naming convention and mapping Security issues Workgroup topology or centralized server Comparison to file transfer Comparison to file synchronization See also References Common file systems and protocols Shared file and printer access require an operating system on the client that supports access to resources on a server, an operating system on the server that supports access to its resources from a client, and an application layer (in the four or five layer TCP/IP reference model) file sharing protocol and transport layer protocol to provide that shared access.
    [Show full text]
  • Resource Management in Multimedia Networked Systems
    University of Pennsylvania ScholarlyCommons Technical Reports (CIS) Department of Computer & Information Science May 1994 Resource Management in Multimedia Networked Systems Klara Nahrstedt University of Pennsylvania Ralf Steinmetz University of Pennsylvania Follow this and additional works at: https://repository.upenn.edu/cis_reports Recommended Citation Klara Nahrstedt and Ralf Steinmetz, "Resource Management in Multimedia Networked Systems ", . May 1994. University of Pennsylvania Department of Computer and Information Science Technical Report No. MS-CIS-94-29. This paper is posted at ScholarlyCommons. https://repository.upenn.edu/cis_reports/331 For more information, please contact [email protected]. Resource Management in Multimedia Networked Systems Abstract Error-free multimedia data processing and communication includes providing guaranteed services such as the colloquial telephone. A set of problems have to be solved and handled in the control-management level of the host and underlying network architectures. We discuss in this paper 'resource management' at the host and network level, and their cooperation to achieve global guaranteed transmission and presentation services, which means end-to-end guarantees. The emphasize is on 'network resources' (e.g., bandwidth, buffer space) and 'host resources' (e.g., CPU processing time) which need to be controlled in order to satisfy the Quality of Service (QoS) requirements set by the users of the multimedia networked system. The control of the specified esourr ces involves three actions: (1) properly allocate resources (end-to-end) during the multimedia call establishment, so that traffic can flow according to the QoS specification; (2) control resource allocation during the multimedia transmission; (3) adapt to changes when degradation of system components occurs.
    [Show full text]
  • Novell Cluster Services,. for Linux. and Netware
    Novell Cluster Services,. for Linux. and NetWare. ROB BASTIAANSEN SANDER VAN VUGT Novell PRESS. Novell. Published by Pearson Education, Inc. 800 East 96th Street, Indianapolis, Indiana 46240 USA Table of Contents Introduction 1 CHAPTER 1: Introduction to Clustering and High Availability 5 Novell Cluster Services Defined 5 Shared Disk Access 6 Secondary IP Addresses 7 Clustering Terminology 8 High-Availability Solutions Overview 12 Novell Cluster Services 12 Business Continuity Clustering 13 PolyServe Matrix Server 15 Heartbeat Subsystem for High-Availability Linux 16 When Not to Cluster Applications 16 Availability Defined 18 High Availability Defined 18 Calculating Average Downtime 21 Avoiding Downtime 22 Hardware 22 Environment 23 Software 23 Procedures 24 Novell Cluster Services Requirements 24 Hardware Requirements 24 Software Requirements 26 CHAPTER 2: Examining Novell Cluster Services Architecture 27 Novell Cluster Services Objects and Modules 27 Cluster eDirectory Objects 28 Cluster Modules 31 IH Novell Cluster Services for Linux and NetWare Heartbeats, Epoch Numbers, and the Split Brain Detector 35 Removing a Failing Slave Node 36 Removing a Failed Master Node 37 Summary 37 CHAPTER 3: Clustering Design 39 Cluster Design Guidelines 39 How Many Nodes to Choose 39 Using a Heartbeat LAN or Not 40 Use NIC Teaming 41 Choosing Storage Methods 42 Mirror the Split Brain Detector Partition 48 Selecting Applications to Run in a Cluster 48 eDirectory Cluster Guidelines 50 Creating a Failover Matrix 52 Application-Specific Design Guidelines
    [Show full text]
  • Novell® Platespin® Recon 3.7.4 User Guide 5.6.4 Printing and Exporting Reports
    www.novell.com/documentation User Guide Novell® PlateSpin® Recon 3.7.4 September 2012 Legal Notices Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on exporting Novell software.
    [Show full text]
  • The Application Usage and Risk Report an Analysis of End User Application Trends in the Enterprise
    The Application Usage and Risk Report An Analysis of End User Application Trends in the Enterprise 8th Edition, December 2011 Palo Alto Networks 3300 Olcott Street Santa Clara, CA 94089 www.paloaltonetworks.com Table of Contents Executive Summary ........................................................................................................ 3 Demographics ............................................................................................................................................. 4 Social Networking Use Becomes More Active ................................................................ 5 Facebook Applications Bandwidth Consumption Triples .......................................................................... 5 Twitter Bandwidth Consumption Increases 7-Fold ................................................................................... 6 Some Perspective On Bandwidth Consumption .................................................................................... 7 Managing the Risks .................................................................................................................................... 7 Browser-based Filesharing: Work vs. Entertainment .................................................... 8 Infrastructure- or Productivity-Oriented Browser-based Filesharing ..................................................... 9 Entertainment Oriented Browser-based Filesharing .............................................................................. 10 Comparing Frequency and Volume of Use
    [Show full text]
  • Characterizing Peer-Level Performance of Bittorrent
    Characterizing Peer-level Performance of BitTorrent DRP Report Amir H. Rasti ABSTRACT 1. INTRODUCTION BitTorrent is one of the most popular Peer-to-Peer During the past few years, peer-to-peer appli- (P2P) content distribution applications over the cations have become very popular on the In- Internet that significantly contributes in network ternet. BitTorrent in one of the most popu- traffic. lar peer-to-peer applications providing scalable peer-to-peer content distribution over the In- In BitTorrent, a file is divided into segments ternet. Some recent studies [8] have shown that and participating peers contribute their outgoing BitTorrent is accountable for approximately bandwidth by providing their available segments 35% of the Internet traffic. BitTorrent is a to other peers while obtaining their missing peers scalable peer-to-peer content distribution sys- from others. Characterization of BitTorrent is use- tem that enables one-to-many distribution of ful in determining its performance bottlenecks as large files without requiring a large access link well as its impact on the network. bandwidth at the source. Similar to other peer- In this study, we try to address the following two to-peer systems, it uses resources of participat- key questions through measurement: (i) What are ing peers to increase the capacity of the system. the main factors that affect observed performance The main shared resource in BitTorrent is the by individual peers in BitTorrent?, and (ii) What up-link bandwidth of individual peers. The file are the contributions of these factors on the per- being distributed is divided into a large number formance of individual peers? To address these of segments.
    [Show full text]
  • Server I/O Networks Past, Present, and Future Renato John Recio Chief Architect, IBM Eserver I/O IBM Systems Group, Austin, Texas [email protected]
    Server I/O Networks Past, Present, and Future Renato John Recio Chief Architect, IBM eServer I/O IBM Systems Group, Austin, Texas [email protected] Abstract • Low latency - the total time required to transfer the first bit of a message from the local application to the remote appli- Enterprise and technical customers place a diverse set of cation, including the transit times spent in intermediate requirements on server I/O networks. In the past, no single switches and I/O adapters. network type has been able to satisfy all of these requirements. As • High throughput - the number of small block transactions a result several fabric types evolved and several interconnects performed per second. The size and rate of small block I/O emerged to satisfy a subset of the requirements. Recently several depends on the workload and fabric type. A first level technologies have emerged that enable a single interconnect to be approximation of the I/O block size and I/O throughput rates required for various I/O workloads can be found in used as more than one fabric type. This paper will describe the “I/O Workload Characteristics of Modern Servers” [4]. requirements customers place on server I/O networks; the various • High bandwidth - the number of bytes per second sup- fabric types and interconnects that have been used to satisfy those ported by the network. Typically, used to gauge perfor- requirements; the technologies that are enabling network mance for large block data transfers. Peek bandwidth convergence; and how these new technologies are being deployed describes the bandwidth provided by a given link; whereas on various network families.
    [Show full text]
  • Dictionary of Health Information Technology and Security
    DICTIONARY OF HEALTH INFORMATION TECHNOLOGY AND SECURITY Dr. David Edward Marcinko, MBA , CFP© Certifi ed Medical Planner© Editor-in-Chief Hope Rachel Hetico, RN, MSHA, CPHQ Certifi ed Medical Planner© Managing Editor NEW YORK 33021009_FM1.indd021009_FM1.indd i 003/17/20073/17/2007 116:48:506:48:50 Copyright © 2007 Springer Publishing Company, LLC All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmit- ted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior permission of Springer Publishing Company, LLC. Springer Publishing Company, LLC 11 West 42nd Street New York, NY 10036 www.springerpub.com Acquisitions Editor: Sheri W. Sussman Production Editor: Carol Cain Cover design: Mimi Flow Composition: Apex Publishing, LLC 07 08 09 10/ 5 4 3 2 1 Library of Congress Cataloging-in-Publication Data Dictionary of health information technology and security / David Edward Marcinko, editor-in-chief, Hope Rachel Hetico, managing editor. p. ; cm. Includes bibliographical references. ISBN-13: 978-0-8261-4995-4 (alk. paper) ISBN-10: 0-8261-4995-2 (alk. paper) 1. Medical informatics—Dictionaries. 2. Medicine—Information technology—Dictionaries. 3. Medical informatics—Security measures— Dictionaries. I. Marcinko, David E. (David Edward) II. Hetico, Hope R. [DNLM: 1. Informatics—Dictionary—English. 2. Medical Informatics— Dictionary—English. 3. Computer Communication Networks—Dictionary— English. 4. Computer Security—Dictionary—English. W 13 D557165 2007] R858.D53 2007 610.3—dc22 2007005879 Printed in the United States of America by RR Donnelley. 33021009_FM1.indd021009_FM1.indd iiii 003/17/20073/17/2007 116:48:516:48:51 Th e Dictionary of Health Information Technology and Security is dedicated to Edward Anthony Marcinko Sr., and Edward Anthony Marcinko Jr., of Fell’s Point, Maryland.
    [Show full text]
  • Ifolder Professional Edition
    Quick Start July 16, 200263 To begin a Quick Start (English): Click in the box under the word Novell. Insert Quick Start and Title elements. 2. Type the product name. 3. Insert the HeadQS element, type the title of your card. 4. (Optional) Put product version on the card: Click View > Master Pages. Click in the small text box at the far left of the decorative lines. Click Tools > Variable > select the variable named Version > Edit Definition > enter the version number > click Done > Insert. It will appear as background text. Click View > Body Pages to return. For a single (stand-alone) card: Keep this master page, named “QS-Single.“ It shows the part number on the bottom right, since single cards don’t have front matter. For a card that’s part of a booklet: Use Print Preparation > Format > Page Layout > Master Page Usage to change to using “First” master page on the first page of the card. It doesn’t show the part number, since part number will be noted in the front of the booklet. Novell iFolder Professional Edition 2.0 www.novell.com QUICK START iFolder Quick Start Welcome to the Novell® iFolderTM Professional Edition Quick Start. This guide covers the following topics: ! “Overview” on page 1 ! “Installing the iFolder Client” on page 2 ! “Accessing iFolder through a Web Browser” on page 4 ! “Using iFolder” on page 5 ! “Tips and tricks for Synchronizing” on page 6 ! “Frequently Asked Questions” on page 8 OVERVIEW Novell iFolder lets you access your files from anywhere, at any time. It no longer matters where you are; iFolder lets you open and use any local files that you’ve placed in your iFolder directory.
    [Show full text]