DOCSLIB.ORG

Netshow CLI / Netshow Library - Linux Provider Release 1.1.7+Git.18.C727438

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Netshow CLI / Netshow Library - Linux Provider Release 1.1.7+Git.18.C727438 Netshow CLI / Netshow Library - Linux Provider Release 1.1.7+git.18.c727438 Jun 20, 2017 Contents 1 Netshow Linux Provider 1 1.1 Linux Provider API...........................................1 1.1.1 Linux Provider API - Netshow Library.............................1 1.1.2 Linux Provider API - Netshow App.............................. 13 1.2 License.................................................. 19 1.3 Credits.................................................. 19 Python Module Index 21 i ii CHAPTER 1 Netshow Linux Provider The Netshow Linux Provider is a plugin for the Netshow, a linux troubleshooting toolkit This site contains the API for this provider. For more details on how Netshow works, see the Netshow App Intro and Netshow Library Intro Linux Provider API Linux Provider API - Netshow Library netshowlib.linux.bond module This module is responsible for finding properties related to bond interface and bond member interfaces class netshowlib.linux.bond.Bond(name, cache=None) Bases: netshowlib.linux.iface.Iface Linux Bond attributes •members: list of bond members/slaves. creates instances of BondMember •bond mode: options are –balance-rr ‘0’ –active-backup ‘1’ –balance-xor ‘2’ –balance-alb ‘3’ –802.3ad ‘4’ –balance-tlb ‘5’ –balance-alb ‘6’ •min_links: number of minimum links 1 Netshow CLI / Netshow Library - Linux Provider, Release 1.1.7+git.18.c727438 •hash_policy: load balancing algorithm. options are –layer2 ‘0’ –layer3+4 ‘1’ •lacp: pointer to Lacp instance for this bond •system_mac: Bond system mac. Packets egressing bond use this mac address. bridge_masters Returns list of bridges associated with this port and its subinterfaces. hash_policy Returns bond load balancing policy / xmit hash policy lacp Returns linux.lacp class instance if bond is in LACP mode members Returns list of bond members min_links Returns number of minimum links required to keep the bond active mode Returns bond mode integer. Not the name. See linux kernel driver docs for more details stp Returns KernelStpBridgeMember instance system_mac Returns bond system mac class netshowlib.linux.bond.BondMember(name, cache=None, master=None) Bases: netshowlib.linux.iface.Iface Linux Bond Member Attributes •master: pointer to Bond instance that this interface belongs to. This can be provided in the __init__ function •linkfailures: bond driver reports number of times bond member flaps •bondstate: returns whether bond member is active (1) or inactive(0) in a bond irrespective of its car- rier/linkstate status. What this means is that the link can be up, but not in the bond. Examples: import netshowlib.netshowlib as nn # bond member info should be normally obtained from # first calling the bond and then running the members # property. bond0= nn.bond.Bond('bond0') print len(bond0.members.keys()) >>2 # on the rare case you know the bond member but want to get # bond master information you can. 2 Chapter 1. Netshow Linux Provider Netshow CLI / Netshow Library - Linux Provider, Release 1.1.7+git.18.c727438 bondmem= nn.bond_member.BondMember('eth1') print bondmem.master >> Linux Bond Interface'bond0'. Member Count:1 bondstate Returns state of interface in the bond. can be 0(inactive) or 1(active) linkfailures number of mii transitions bond member reports while the bond is active this counter cannot be cleared. will reset when the bond is reinitialized via the ifdown/ifup process Returns number of mii transitions master Returns pointer to Bond instance that this interface belongs to netshowlib.linux.bridge module This module is responsible for finding properties related to linux bridge and bridge member interfaces class netshowlib.linux.bridge.Bridge(name, cache=None) Bases: netshowlib.linux.iface.Iface Linux Bridge interface attributes •tagged_members: list of tagged bridge members (part of a trunk) •untagged_members: list of untagged bridge members (access) •members: all bridge members •vlan_tag: vlan ID tag if applicable. empty string means no tag. •stp: pointer to KernelStpBridge instance. If set to None, then bridge has STP disabled. members Returns list of bridge port members stp Returns None if STP is disabled Returns KernelStpBridge instance if STP is enabled tagged_members Works for default/classic linux bridge driver Returns list of tagged bridge members. untagged_members Works for default/classic linux bridge driver Returns list of untagged bridge members vlan_tag For the classic/default bridge driver, if a tagged bridge member is provided then the function will use the tag as the vlan id Returns vlan ID if applicable. If multiple tags found, 1.1. Linux Provider API 3 Netshow CLI / Netshow Library - Linux Provider, Release 1.1.7+git.18.c727438 possibly indicating vlan translation, then all tags are printed as a list Empty array means no tag class netshowlib.linux.bridge.BridgeMember(name, cache=None) Bases: netshowlib.linux.iface.Iface Linux Bridge Member attributes •cache: feature cache •stp: pointer to KernelStpBridgeMember instance bridge_masters Returns list of bridges associated with this port and its subinterfaces. stp Returns instance of KernelStpBridgeMember class netshowlib.linux.bridge.KernelStpBridge(bridge) Bases: object Attributes for STP for a bridge •bridge: instance of Bridge •member_state: return hash of basic stp attributes of bridge members. Example iface= linux.bridge.Bridge('eth2') iface.stp.state >>{'stp_disabled':[list of bridge member instances] 'forwarding':[list of bridge member instances ] 'blocking':[list of bridge member instances ] 'intransition':[ list of bridge member instances ] 'disabled':[list of bridge member instances] 'root':[list of bridge member instances. should only be one] } •root_priority: root priority for the spanning tree domain •bridge_priority: bridge priority bridge_priority Returns return bridge priority number is_root() Returns True if bridge is STP root. member_state Returns dict of stp state of bridge members root_priority Returns return root priority number class netshowlib.linux.bridge.KernelStpBridgeMember(bridgemem, cache=None) Bases: object Attributes for Bridgemems using the Kernel STP •bridgemem: instance of BridgeMember •state: return hash of basic stp attributes of the port. Example 4 Chapter 1. Netshow Linux Provider Netshow CLI / Netshow Library - Linux Provider, Release 1.1.7+git.18.c727438 iface= linux.bridge.BridgeMember('eth2') iface.stp.state >>{'forwarding':[list of bridge instances ] 'blocking':[list of bridge instances ] 'intransition':[ list of bridge instances ] 'disabled':[list of bridge instances] 'root':[list of bridges instances with root ports ] 'stp_disabled':[ list of bridge instances where stp is disabled] } •cache: feature cache that is used state Returns dict of stp states with associated linux.bridge instances netshowlib.linux.bridge.update_stp_state(stp_hash, iface_to_add, iface_under_test) Updates stp state dict from BridgeMember and Bridge netshowlib.linux.cache module This module produces the cache info for Linux class netshowlib.linux.cache.Cache Bases: object This class produces the cache info for Linux networking such as ip addressing, lldp, QOS run(features=None) Parameters features – List of features to enable. If set to None cache from all features is obtained Returns returns Cache instance of appropriate OS type netshowlib.linux.common module Linux common module exception netshowlib.linux.common.ExecCommandException Bases: exceptions.Exception Exception when a exec command fails netshowlib.linux.common.check_bit(int_type, offset) copied from wiki.python.org if testBit is not zero, return checkBit as True netshowlib.linux.common.clear_bit(int_type, offset) Returns integer with the bit at ‘offset’ cleared netshowlib.linux.common.create_range(rkey, rgroup) Parameters rkey – if rey is swp, rgroup is “swp2, swp3, swp10” create a range list given a list of ports with a common pattern netshowlib.linux.common.create_sort_tuple(result) returns tuple value used for sorting. Example (‘bond’, ‘0’, ‘.’ , ‘1’) converts it to (‘bond’, 0, 0, 1) for the sort another example (‘vlan’, ‘10’, ‘-v’, ‘0’) converts to (‘vlan’, 10, 0, 0) for the sort. 1.1. Linux Provider API 5 Netshow CLI / Netshow Library - Linux Provider, Release 1.1.7+git.18.c727438 netshowlib.linux.common.dict_merge(list1, list2) merge two dicts by overriding content in first dict with content from 2nd dict. does not return a new merge dict. all merging takes place in the first dict. Parameters • list1 – original dict • list2 – dict to override original dict content netshowlib.linux.common.exec_command(cmd, cmdenv=None) execute a command netshowlib.linux.common.exec_commandl(cmdl, cmdenv=None) execute a command netshowlib.linux.common.generate_cidr_ip(addr) generate address in CIDR format Example: 10.1.1.1/24 instead of 10.1.1.1 mask 255.255.255.0 netshowlib.linux.common.group_iface(initial_list, group_func) groups iface values netshowlib.linux.common.group_ports(list_of_ports) create group list of ports given a list of ports. Example: ‘swp1, swp2, bond0, bond1, swp3.100, swp4.100’ becomes ‘swp1-2, swp3-4.100, bond0-1’ netshowlib.linux.common.grouping_func(xvar) group ports based on 2 criteria. If name is like so ‘bond0’, ‘swp22’, ‘br-vlan22’, ‘vlan33’, group it by name. So for example ‘bond0’, ‘bond1’, would be under the ‘bond’ group. 2nd criteria is by vlan number. If the ports are ‘swp1.100, swp2.100’ group it by ‘100’. So Dict entry would be ‘100’ -> ‘swp1.100’, ‘swp2.100’ netshowlib.linux.common.has_stats(ifacename) netshowlib.linux.common.munge_str(match0) sorting by string that is int, produces wrong sort..so
Load more

Recommended publications
  • Case Study: Internet Explorer 1994..1997
    Case Study: Internet Explorer 1994..1997 Ben Slivka General Manager Windows UI [email protected] Internet Explorer Chronology 8/94 IE effort begins 12/94 License Spyglass Mosaic source code 7/95 IE 1.0 ships as Windows 95 feature 11/95 IE 2.0 ships 3/96 MS Professional Developer’s Conference AOL deal, Java license announced 8/96 IE 3.0 ships, wins all but PC Mag review 9/97 IE 4.0 ships, wins all the reviews IE Feature Chronology IE 1.0 (7/14/95) IE 2.0 (11/17/95) HTML 2.0 HTML Tables, other NS enhancements HTML <font face=> Cell background colors & images Progressive Rendering HTTP cookies (arthurbi) Windows Integration SSL Start.Run HTML (MS enhancements) Internet Shortcuts <marquee> Password Caching background sounds Auto Connect, in-line AVIs Disconnect Active VRML 1.0 Navigator parity MS innovation Feature Chronology - continued IE 3.0 (8/12/96) IE 3.0 - continued... IE 4.0 (9/12/97) Java Accessibility Dynamic HTML (W3C) HTML Frames PICS (W3C) Data Binding Floating frames HTML CSS (W3C) 2D positioning Componentized HTML <object> (W3C) Java JDK 1.1 ActiveX Scripting ActiveX Controls Explorer Bars JavaScript Code Download Active Setup VBScript Code Signing Active Channels MSHTML, SHDOCVW IEAK (corporations) CDF (XML) WININET, URLMON Internet Setup Wizard Security Zones DocObj hosting Referral Server Windows Integration Single Explorer ActiveDesktop™ Navigator parity MS innovation Quick Launch, … Wins for IE • Quality • CoolBar, Explorer Bars • Componetization • Great Mail/News Client • ActiveX Controls – Outlook Express – vs. Nav plug-ins
    [Show full text]
  • Planning for Internet Explorer and the IEAK
    02_Inst.fm Page 15 Monday, October 16, 2000 9:40 AM TWO 2Chapter 2 Planning for Internet Explorer and the IEAK LChapter Syllabus In this chapter, we will look at material covered in the Planning section of Microsoft’s Implementing MCSE 2.1 Addressing Technical Needs, Rules, and Policies and Supporting Microsoft Internet Explorer 5 by using the Internet Explorer Administration Kit exam MCSE 2.2 Planning for Custom (70-080). After reading this chapter, you should be Installations and Settings able to: MCSE 2.3 Providing Multiple • Identify and evaluate the technical needs of business Language Support units, such as Internet Service Providers (ISPs), con- tent providers, and corporate administrators. MCSE 2.4 Providing Multiple Platform Support • Design solutions based on organizational rules and policies for ISPs, content providers, and corporate MCSE 2.5 Developing Security Strategies administrators. • Evaluate which components to include in a custom- MCSE 2.6 Configuring for Offline ized Internet Explorer installation package for a given Viewing deployment scenario. MCSE 2.7 Replacing Other Browsers • Develop appropriate security strategies for using Internet Explorer at various sites, including public MCSE 2.8 Developing CMAK kiosks, general business sites, single-task-based sites, Strategies and intranet-only sites. 15 02_Inst.fm Page 16 Monday, October 16, 2000 9:40 AM 16 Chapter 2 • Planning for Internet Explorer and the IEAK • Configure offline viewing for various types of users, including gen- eral business users, single-task users, and mobile users. • Develop strategies for replacing other Internet browsers, such as Netscape Navigator and previous versions of Internet Explorer. • Decide which custom settings to configure for Microsoft Outlook Express for a given scenario.
    [Show full text]
  • NBAR2 Standard Protocol Pack 1.0
    NBAR2 Standard Protocol Pack 1.0 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 © 2013 Cisco Systems, Inc. All rights reserved. CONTENTS CHAPTER 1 Release Notes for NBAR2 Standard Protocol Pack 1.0 1 CHAPTER 2 BGP 3 BITTORRENT 6 CITRIX 7 DHCP 8 DIRECTCONNECT 9 DNS 10 EDONKEY 11 EGP 12 EIGRP 13 EXCHANGE 14 FASTTRACK 15 FINGER 16 FTP 17 GNUTELLA 18 GOPHER 19 GRE 20 H323 21 HTTP 22 ICMP 23 IMAP 24 IPINIP 25 IPV6-ICMP 26 IRC 27 KAZAA2 28 KERBEROS 29 L2TP 30 NBAR2 Standard Protocol Pack 1.0 iii Contents LDAP 31 MGCP 32 NETBIOS 33 NETSHOW 34 NFS 35 NNTP 36 NOTES 37 NTP 38 OSPF 39 POP3 40 PPTP 41 PRINTER 42 RIP 43 RTCP 44 RTP 45 RTSP 46 SAP 47 SECURE-FTP 48 SECURE-HTTP 49 SECURE-IMAP 50 SECURE-IRC 51 SECURE-LDAP 52 SECURE-NNTP 53 SECURE-POP3 54 SECURE-TELNET 55 SIP 56 SKINNY 57 SKYPE 58 SMTP 59 SNMP 60 SOCKS 61 SQLNET 62 SQLSERVER 63 SSH 64 STREAMWORK 65 NBAR2 Standard Protocol Pack 1.0 iv Contents SUNRPC 66 SYSLOG 67 TELNET 68 TFTP 69 VDOLIVE 70 WINMX 71 NBAR2 Standard Protocol Pack 1.0 v Contents NBAR2 Standard Protocol Pack 1.0 vi CHAPTER 1 Release Notes for NBAR2 Standard Protocol Pack 1.0 NBAR2 Standard Protocol Pack Overview The Network Based Application Recognition (NBAR2) Standard Protocol Pack 1.0 is provided as the base protocol pack with an unlicensed Cisco image on a device.
    [Show full text]
  • Microsoft Palladium
    Microsoft Palladium: A Business Overview Combining Microsoft Windows Features, Personal Computing Hardware, and Software Applications for Greater Security, Personal Privacy, and System Integrity by Amy Carroll, Mario Juarez, Julia Polk, Tony Leininger Microsoft Content Security Business Unit June 2002 Legal Notice This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred.
    [Show full text]
  • View Publication
    Challenges to Building Scalable Services A Survey of Microsoft’s Internet Services MSR-TR-2015-29 Comments from the Authors: This paper was originally circulated as a Microsoft Confidential memo in fall 1999. Its purpose was to document the findings of the co-authors as we attempted to understand the state-of-the-art of large internet services. Our original intent was to gather the data documented in this paper purely for our own to understand. However, as we discussed early findings with our colleagues, we quickly realized the value of circulating them to a wider audience. The original memo was circulated to Microsoft’s entire executive staff and quickly passed around. From file server data, we believe over 1,000 MS employees read the original memo in the first three months after internal publication. This release of the memo has been modified slightly from the original to remove non- technical information, such as business plans. Due to an unfortunate oversight on my part, the original memo did not name each of the people we interviewed. Those pioneers deserved recognition at the time and their groundbreaking work deserves now to be remembered by history. In the 15 years since this paper’s circulation, much has changed at Microsoft and in the industry. Experience gathered in writing this paper directly lead to our discovery of the core principles of what is now widely known as cloud computing. In 1999, Microsoft’s largest internet service had just over 2,000 computers. Today, many cloud services use over 100,000 servers. Many of the services and technologies described in this paper no longer exist.
    [Show full text]
  • Assessing the Feasibility of Using Microsoft Netmeeting in Distance
    Assessing the Feasibility of Using Microsoft® NetMeetingTM in Distance Education Oge Marques and Sam Hsu‡ Abstract ¾ One of the weaknesses of most Web-based distance education systems is the lack of adequate, synchronous, interac- II. DESCRIPTION OF THE PRODUCT tion between instructor and students. An easy and inexpensive solution to this problem can be obtained by using an off-the- Microsoft NetMeeting can be described as a collaboration shelf collaboration tool. In this paper we examine one of those tools, Microsoft tool that combines voice and data communications, video, NetMeeting. NetMeeting’s main technical features, pros and real-time application sharing, file transfer, a full-featured cons are presented and its suitability for educational applica- shared whiteboard, and text based chat [21]. tions is evaluated. Based on the collected facts, a recommenda- NetMeeting is targeted at home users, as well as small and tion for the decision-maker is presented at the end of the article. large organizations and claims to allow users to “take full advantage of the global reach of the Internet or corporate Index Terms ¾ Web-based education, distance learning, col- intranet for real-time communications and collaboration.” [1] laboration tools, conferencing. Connecting to other NetMeeting users is made easy with the Microsoft Internet Locator Server (ILS), enabling participants I. INTRODUCTION to call each other from a dynamic directory within Net- Meeting or from a Web page. Connections can also be estab- One of the most criticized aspects of distance education lished by calling the other party’s IP address. While con- (both conventional as well as Web-based) is the lack of syn- nected on the Internet or corporate intranet, participants can chronous, real-time, “live” interaction between instructor and communicate with audio and video, work together on virtu- students.
    [Show full text]
  • Release Notes for NBAR2 Protocol Pack 37.0.0 for Cisco Wireless Controllers
    Release Notes for NBAR2 Protocol Pack 37.0.0 for Cisco Wireless Controllers • Overview, on page 2 • Supported Platforms, on page 3 • New Protocols in NBAR2 Protocol Pack 37.0.0, on page 4 • Updated Protocols in NBAR2 Protocol Pack 37.0.0, on page 10 • Deprecated Protocols in NBAR2 Protocol Pack 37.0.0, on page 16 • Caveats in NBAR2 Protocol Pack 37.0.0, on page 17 • Downloading NBAR2 Protocol Pack 37.0.0, on page 20 • Special Notes and Limitations, on page 21 Release Notes for NBAR2 Protocol Pack 37.0.0 for Cisco Wireless Controllers 1 Release Notes for NBAR2 Protocol Pack 37.0.0 for Cisco Wireless Controllers Overview Overview The NBAR2 Protocol Pack 37.0.0 release includes: • New protocols • Updated protocols • Classification improvements • Bug fixes Release Notes for NBAR2 Protocol Pack 37.0.0 for Cisco Wireless Controllers 2 Release Notes for NBAR2 Protocol Pack 37.0.0 for Cisco Wireless Controllers Supported Platforms Supported Platforms Network-Based Application Recognition (NBAR2) Protocol Pack 37.0.0 support is provided on the following Cisco Wireless Controller platforms. • Cisco 3504 Wireless Controller • Cisco 5520 Wireless Controller • Cisco 8540 Wireless Controller • Cisco Virtual Wireless Controller (vWLC) on the following platforms • VMware vSphere Hypervisor (ESXi) Version 5.x and 6.x • Hyper-V on Microsoft Servers 2012 and later versions (Support introduced in Release 8.4) • Kernel-based virtual machine (KVM) (Support introduced in Release 8.1. After KVM is deployed, we recommend that you do not downgrade to a Cisco Wireless release that is earlier than Release 8.1.) • Cisco Wireless Controllers for High Availability for Cisco 3504 controller, Cisco 5520 controller, and Cisco 8540 controller.
    [Show full text]
  • Readme for Ciscoworks LAN Management Solution 3.2 Service Pack 1
    Readme for CiscoWorks LAN Management Solution 3.2 Service Pack 1 Revised: Mar, 2011, OL-24538-01 Contents This document provides instructions for downloading and installing CiscoWorks LAN Management Solution (LMS) 3.2 Service Pack 1. It also provides information to the known problems in LMS 3.2 Service Pack1. This document has the following sections: • Description • Hardware and Software Requirements • Prerequisites for CiscoWorks LAN Management Solution 3.2 Service Pack 1 • Downloading CiscoWorks LAN Management Solution 3.2 Service Pack 1 • Installing CiscoWorks LAN Management Solution 3.2 Service Pack 1 • Installing Remote Syslog Collector • Verifying the Installation • Data Migration Notes • Known Problems in Ciscoworks LMS 3.2 SP1 • Support for MDF 1.47 • Resolved Problems in CiscoWorks LMS 3.2 SP1 • CiscoWorks LAN Management Solution 3.2 Service Pack 1 Related Documentation • Obtaining Documentation, Obtaining Support, and Security Guidelines • Notices Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA Description Description CiscoWorks LAN Management Solution 3.2 Service Pack 1 is a service pack release and contains solutions to the known problems of CiscoWorks LAN Management Solution 3.2. CiscoWorks LAN Management Solution 3.2 Service Pack 1 consists of a single mega patch installation for application releases on top of LMS 3.2. This release focusses primarily on providing critical bug fixes and Day 1 device support merges. The following applications are part of the mega patch install: • Cisco Works Common Services 3.3.1 • Campus Manager 5.2.2 • Resource Manager Essentials 4.3.2 • Health and Utilization Monitor 1.2.2 • Internetwork Performance Monitor 4.2.1 • Device Fault Manager 3.2.1 • LMS Portal 1.2.1 CiscoWorks LAN Management Solution 3.2 should be installed before installing CiscoWorks LAN Management Solution 3.2 SP1.
    [Show full text]
  • Moving from Moos to Multi-User Applications Steven M
    Moving from MOOs to Multi-User Applications Steven M. Drucker Virtual Worlds Group Microsoft Research Microsoft Corporation Abstract limitations when the user interface is extended to include multi-media. This paper provides a brief description of the work we have done on the V-Worlds project, a system that In this paper I will address the limitations of prior work, facilitates the creation of multi-user applications and highlight the unique features of our current work and environments. We have taken concepts originally found discuss applications of this system. in object oriented Multi-User Dungeons (MOOs) and 2. Background and related work extended them to deal with more general multi-user and in particular multi-media applications. We present An object-oriented MUD, such as White and Curtis’ reasons behind the architectural decisions of the MOO [1,2], is a network database server that stores platform and show that it has been used successfully for objects having properties and methods. The topology of a wide range of examples. the space is defined by “room” objects, representing discrete locations, interconnected by portal objects. Keywords Objects in a MOO can also represent things located in a MOOs, Virtual Environments, Rapid Prototyping, room, and objects called “players” or “avatars” Shared environments, Multiuser Applications, DIS, represent the user’s character in the world and are CSCW, Distance Learning, DHTML, ActiveX. intimately associated with a user’s connection into the 1. Introduction world. Users in the same room are able to talk by typing text and reading the text that others type. Each MUD Computers are increasingly being used as room is superficially similar to an Internet chat room or communication devices as opposed to only information IRC channel, but there is no persistence of objects or processing and retrieval devices.
    [Show full text]
  • Introduction to Vmware Thinapp Vmware Thinapp 4.0 Introduction to Vmware Thinapp
    Introduction to VMware ThinApp VMware ThinApp 4.0 Introduction to VMware ThinApp Introduction to VMware ThinApp Revision: 20080627 Item: EN-000063-00 You can find the most up-to-date technical documentation on our Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: [email protected] © 2008 VMware, Inc. All rights reserved. Protected by one or more U.S. Patent Nos. 6,397,242, 6,496,847, 6,704,925, 6,711,672, 6,725,289, 6,735,601, 6,785,886, 6,789,156, 6,795,966, 6,880,022, 6,944,699, 6,961,806, 6,961,941, 7,069,413, 7,082,598, 7,089,377, 7,111,086, 7,111,145, 7,117,481, 7,149,843, 7,155,558, 7,222,221, 7,260,815, 7,260,820, 7,269,683, 7,275,136, 7,277,998, 7,277,999, 7,278,030, 7,281,102, 7,290,253, and 7,356,679; patents pending. VMware, the VMware “boxes” logo and design, Virtual SMP and VMotion are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com 2 VMware, Inc. Contents Introduction to VMware ThinApp 5 How ThinApp Works 5 Features of Thinapp 8 User Mode Operation 8 Virtual Side‐By‐Side (SxS) Support 8 Application Isolation 9 Multiple Simultaneous Client Application Versions 9 Instant Portable Deployment of Applications on USB Flash or CD‐ROM) 9 ThinApp Applications Are Loaded as Normal Applications
    [Show full text]
  • PLAYER 2 Or " CLENT 30 U.S
    USOO6239793B1 (12) United States Patent (10) Patent No.: US 6,239,793 B1 Barnert et al. (45) Date of Patent: May 29, 2001 (54) METHOD AND APPARATUS FOR 6,047,317 4/2000 Bisdikian et al. ................... 345/327 SYNCHRONIZING THE BROADCAST 6,052,715 4/2000 Fukui et al. ......................... 709/217 CONTENT OF INTERACTIVE 6,085,227 7/2000 Edlund et al. ....................... 709/203 INTERNET-BASED PROGRAMS 6,151,632 : 11/2000 Chaddha et al. - - - - - - - - - - - - - - - - - - - - - 709/231 (75) Inventors: Andrew Barnert, Hollywood; Kelly OTHER PUBLICATIONS Byrd, Sherman Oaks, both of CA (US) Handling Audio and Video Streams in a Distributed Envi O O ronment, Alan Jones, Andrew Hopper, 12/93. (73) Assignee: Rotor Communications Corporation, Multipoint Audio and Video Control for Packet-Based Mul Hollywood, CA (US) timedia Conferencing, Fengmin Gong, MCNC Information (*) Notice: Subject to any disclaimer, the term of this Technologies, 10/94. patent is extended or adjusted under 35 * cited by examiner U.S.C. 154(b) by 0 days. Primary Examiner Heather R. Herndon (21) Appl. No.: 09/315,889 Assistant Examiner-Cong Lac Huynh (74) Attorney, Agent, or Firm-Dickstein Shapiro Morin & (22) Filed: May 20, 1999 Oshinsky LLP (51) Int. Cl." .................................................. G06F 15/00 (57) ABSTRACT (52) U.S. Cl. .......................... 345/302; 345/328; 709/203; 709/231 A method and System for Synchronizing broadcast program (58) Field of Search ............................. 345/302; 709/203, content and corresponding program commands of an 709/231 Internet-Based broadcast. The method (and System) gener ates a plurality of time-indicative index values during a (56) References Cited broadcast of a program, associates ones of the plurality of index values with respective commands in a command U.S.
    [Show full text]
  • MICROSOFT V COMMISSION
    MICROSOFT v COMMISSION JUDGMENT OF THE COURT OF FIRST INSTANCE (Grand Chamber) 17 September 2007 * In Case T-201/04, Microsoft Corp., established in Redmond, Washington (United States), represented by J.-F. Bellis, lawyer, and I. Forrester QC, applicant, supported by The Computing Technology Industry Association, Inc,, established in Oakbrook Terrace, Illinois (United States), represented by G. van Gerven and T. Franchoo, lawyers, and B. Kilpatrick, Solicitor, DMDsecurexom BV, established in Amsterdam (Netherlands), MPS Broadband AB, established in Stockholm (Sweden), Pace Micro Technology plc, established in Shipley, West Yorkshire (United Kingdom), * Language of the case: English. II - 3619 JUDGMENT OF 17. 9. 2007 — CASE T-201/04 Quantel Ltd, established in Newbury, Berkshire (United Kingdom), Tandberg Television Ltd, established in Southampton, Hampshire (United Kingdom), represented by J. Bourgeois, lawyer, Association for Competitive Technology, Inc,, established in Washington, DC (United States), represented by L. Ruessmann and P. Hecker, lawyers, and K. Bacon, Barrister, TeamSystem SpA, established in Pesaro (Italy), Mamut ASA, established in Oslo (Norway), represented by G. Berrisch, lawyer, Exor AB, established in Uppsala (Sweden), represented by S. Martinez Lage, H. Brokelmann and R. Allendesalazar Corcho, lawyers, interveners, II - 3620 MICROSOFT v COMMISSION v Commission of the European Communities, represented initially by R. Wainwright, F. Castillo de la Torre, P. Hellström and A. Whelan, acting as Agents, and subsequently by F. Castillo de la Torre, P. Hellström and A. Whelan, defendant, supported by Software & Information Industry Association, established in Washington, DC, represented by J. Flynn QC, C Simpson and T. Vinje, Solicitors, and D. Paemen, N. Dodoo and M. Dolmans, lawyers, Free Software Foundation Europe eV, established in Hamburg (Germany), represented by C Piana, lawyer, Audiobannerxom, established in Los Angeles, California (United States), represented by L.
    [Show full text]