DOCSLIB.ORG

Diffusion 6.6 User Guide Contents

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Diffusion 6.6 User Guide Contents Diffusion 6.6 User Guide Contents List of Figures..............................................................................................10 List of Tables............................................................................................... 12 Part I: Welcome.......................................................................... 15 Introducing Diffusion................................................................................................. 16 Introducing topics and data................................................................................................ 16 Introducing sessions.............................................................................................................20 What's new in Diffusion 6.6?...................................................................................... 23 Part II: Quick Start Guide............................................................ 26 Part III: Design Guide.................................................................. 27 Support.....................................................................................................................28 System requirements for the Diffusion server....................................................................28 Platform support for the Diffusion API libraries.................................................................31 Feature support in the Diffusion API...................................................................................33 License types.........................................................................................................................38 Protocol support...................................................................................................................39 Browser support................................................................................................................... 40 Browser limitations.............................................................................................................. 41 WebSocket limitations............................................................................................. 41 Cross-origin resource sharing limitations...............................................................41 Browser connection limitations.............................................................................. 42 Designing your data model.........................................................................................43 Topic tree.............................................................................................................................. 43 Topic naming............................................................................................................ 44 Topic selectors..........................................................................................................45 Topic views............................................................................................................... 51 Topics.................................................................................................................................... 65 Properties of topics.................................................................................................. 66 JSON topics...............................................................................................................70 Binary topics............................................................................................................. 72 String topics..............................................................................................................74 Int64 topics............................................................................................................... 76 Diffusion | 2 Double topics............................................................................................................78 Time series topics.....................................................................................................79 Routing topics...........................................................................................................82 Slave topics (DEPRECATED).....................................................................................83 RecordV2 topics........................................................................................................ 85 Pub-sub................................................................................................................................. 89 Publishing data.........................................................................................................90 Subscribing to topics................................................................................................92 Topic notifications................................................................................................................94 Request-response messaging.............................................................................................. 96 Conflation..............................................................................................................................98 Using conflation........................................................................................................98 Designing your solution............................................................................................. 99 Servers................................................................................................................................. 100 Server clusters for high availability...................................................................................101 Session replication................................................................................................. 103 Topic replication.....................................................................................................107 Failover of active update sources......................................................................... 108 Sharing data with remote servers.....................................................................................110 Remote topic views................................................................................................ 111 Fan-out.................................................................................................................... 112 Using missing topic notifications with fan-out.....................................................114 Topic persistence................................................................................................................116 Topic delivery priority........................................................................................................ 118 Automatic topic removal................................................................................................... 118 Clients..................................................................................................................................119 Client types............................................................................................................. 119 Using clients............................................................................................................121 Using clients for control.........................................................................................121 Client coordination.................................................................................................123 User-written components.................................................................................................. 124 Third party components.................................................................................................... 125 Load balancers....................................................................................................... 125 Web servers.............................................................................................................126 JMS.......................................................................................................................... 129 Example solutions.............................................................................................................. 131 Example: Simple solution...................................................................................... 131 Example: A solution using clients..........................................................................132 Example: Scalable and resilient solution..............................................................133 Security...................................................................................................................133 Role-based authorization...................................................................................................134 Permissions............................................................................................................. 138 Pre-defined roles.................................................................................................... 143 Authentication.................................................................................................................... 145 User-written authentication handlers...................................................................149 System authentication handler.............................................................................150 Pre-defined users....................................................................................................151
Load more

Recommended publications
  • Role of Librarian in Internet and World Wide Web Environment K
    Informing Science Information Sciences Volume 4 No 1, 2001 Role of Librarian in Internet and World Wide Web Environment K. Nageswara Rao and KH Babu Defence Research & Development Laboratory Kanchanbagh Post, India [email protected] and [email protected] Abstract The transition of traditional library collections to digital or virtual collections presented the librarian with new opportunities. The Internet, Web en- vironment and associated sophisticated tools have given the librarian a new dynamic role to play and serve the new information based society in bet- ter ways than hitherto. Because of the powerful features of Web i.e. distributed, heterogeneous, collaborative, multimedia, multi-protocol, hyperme- dia-oriented architecture, World Wide Web has revolutionized the way people access information, and has opened up new possibilities in areas such as digital libraries, virtual libraries, scientific information retrieval and dissemination. Not only the world is becoming interconnected, but also the use of Internet and Web has changed the fundamental roles, paradigms, and organizational culture of libraries and librarians as well. The article describes the limitless scope of Internet and Web, the existence of the librarian in the changing environment, parallelism between information sci- ence and information technology, librarians and intelligent agents, working of intelligent agents, strengths, weaknesses, threats and opportunities in- volved in the relationship between librarians and the Web. The role of librarian in Internet and Web environment especially as intermediary, facilita- tor, end-user trainer, Web site builder, researcher, interface designer, knowledge manager and sifter of information resources is also described. Keywords: Role of Librarian, Internet, World Wide Web, Data Mining, Meta Data, Latent Semantic Indexing, Intelligent Agents, Search Intermediary, Facilitator, End-User Trainer, Web Site Builder, Researcher, Interface Designer, Knowledge Man- ager, Sifter.
    [Show full text]
  • S.Tramp Et Al. / an Architecture of a Distributed Semantic Social Network
    Semantic Web 1 (2012) 1–16 1 IOS Press An Architecture of a Distributed Semantic Social Network Sebastian Tramp a;∗, Philipp Frischmuth a, Timofey Ermilov a, Saeedeh Shekarpour a and Sören Auer a a Universität Leipzig, Institut für Informatik, AKSW, Postfach 100920, D-04009 Leipzig, Germany E-mail: {lastname}@informatik.uni-leipzig.de Abstract. Online social networking has become one of the most popular services on the Web. However, current social networks are like walled gardens in which users do not have full control over their data, are bound to specific usage terms of the social network operator and suffer from a lock-in effect due to the lack of interoperability and standards compliance between social networks. In this paper we propose an architecture for an open, distributed social network, which is built solely on Semantic Web standards and emerging best practices. Our architecture combines vocabularies and protocols such as WebID, FOAF, Se- mantic Pingback and PubSubHubbub into a coherent distributed semantic social network, which is capable to provide all crucial functionalities known from centralized social networks. We present our reference implementation, which utilizes the OntoWiki application framework and take this framework as the basis for an extensive evaluation. Our results show that a distributed social network is feasible, while it also avoids the limitations of centralized solutions. Keywords: Semantic Social Web, Architecture, Evaluation, Distributed Social Networks, WebID, Semantic Pingback 1. Introduction platform or information will diverge. Since there are only a few large social networking players, the Web Online social networking has become one of the also loses its distributed nature.
    [Show full text]
  • The History of Spam Timeline of Events and Notable Occurrences in the Advance of Spam
    The History of Spam Timeline of events and notable occurrences in the advance of spam July 2014 The History of Spam The growth of unsolicited e-mail imposes increasing costs on networks and causes considerable aggravation on the part of e-mail recipients. The history of spam is one that is closely tied to the history and evolution of the Internet itself. 1971 RFC 733: Mail Specifications 1978 First email spam was sent out to users of ARPANET – it was an ad for a presentation by Digital Equipment Corporation (DEC) 1984 Domain Name System (DNS) introduced 1986 Eric Thomas develops first commercial mailing list program called LISTSERV 1988 First know email Chain letter sent 1988 “Spamming” starts as prank by participants in multi-user dungeon games by MUDers (Multi User Dungeon) to fill rivals accounts with unwanted electronic junk mail. 1990 ARPANET terminates 1993 First use of the term spam was for a post from USENET by Richard Depew to news.admin.policy, which was the result of a bug in a software program that caused 200 messages to go out to the news group. The term “spam” itself was thought to have come from the spam skit by Monty Python's Flying Circus. In the sketch, a restaurant serves all its food with lots of spam, and the waitress repeats the word several times in describing how much spam is in the items. When she does this, a group of Vikings in the corner start a song: "Spam, spam, spam, spam, spam, spam, spam, spam, lovely spam! Wonderful spam!" Until told to shut up.
    [Show full text]
  • Usenet News HOWTO
    Usenet News HOWTO Shuvam Misra (usenet at starcomsoftware dot com) Revision History Revision 2.1 2002−08−20 Revised by: sm New sections on Security and Software History, lots of other small additions and cleanup Revision 2.0 2002−07−30 Revised by: sm Rewritten by new authors at Starcom Software Revision 1.4 1995−11−29 Revised by: vs Original document; authored by Vince Skahan. Usenet News HOWTO Table of Contents 1. What is the Usenet?........................................................................................................................................1 1.1. Discussion groups.............................................................................................................................1 1.2. How it works, loosely speaking........................................................................................................1 1.3. About sizes, volumes, and so on.......................................................................................................2 2. Principles of Operation...................................................................................................................................4 2.1. Newsgroups and articles...................................................................................................................4 2.2. Of readers and servers.......................................................................................................................6 2.3. Newsfeeds.........................................................................................................................................6
    [Show full text]
  • The Internet and the Web T6 a Technical View of System Analysis and Design
    Technology Guides T1 Hardware T2 Software T3 Data and Databases T4 Telecommunications ᮣ T5 The Internet and the Web T6 A Technical View of System Analysis and Design Technology Guide The Internet 5 and the Web T5.1 What Is the Internet? T5.2 Basic Characteristics and Capabilities of the Internet T5.3 Browsing and the World Wide Web T5.4 Communication Tools for the Internet T5.5 Other Internet Tools T5.1 T5.2 Technology Guide The Internet and the Web T5.1 What Is the Internet?1 The Internet (“the Net”) is a network that connects hundreds of thousands of inter- nal organizational computer networks worldwide. Examples of internal organiza- tional computer networks are a university computer system, the computer system of a corporation such as IBM or McDonald’s, a hospital computer system, or a system used by a small business across the street from you. Participating computer systems, called nodes, include PCs, local area networks, database(s), and mainframes.A node may include several networks of an organization, possibly connected by a wide area network. The Internet connects to hundreds of thousands of computer networks in more than 200 countries so that people can access data in other organizations, and can communicate and collaborate around the globe, quickly and inexpensively. Thus, the Internet has become a necessity in the conduct of modern business. The Internet grew out of an experimental project of the Advanced Research Proj- BRIEF HISTORY ect Agency (ARPA) of the U.S. Department of Defense.The project was initiated in 1969 as ARPAnet to test the feasibility of a wide area computer network over which researchers, educators, military personnel, and government agencies could share data, exchange messages, and transfer files.
    [Show full text]
  • UNDISCLOSED, the State V. Adnan Syed Episode 8 - Ping August 03, 2015
    UNDISCLOSED, the State v. Adnan Syed Episode 8 - Ping August 03, 2015 [0:00] Today’s sponsor is Audible.com. Audible carries over 180,000 audiobooks and spoken ​ word audio products. Get your free audiobook at www.audible.com/undisclosed. ​ ​ [00:15] Support for this show also comes from PicMonkey.com. Since 1738, PicMonkey.com ​ has been the preferred photo editor for everyone from George Washington to your friend with that cool blog. So whether you’re editing photos or creating collages, you can make great stuff with PicMonkey. And now you--yes, you--can have a free trial of PicMonkey’s premium service. It’s a heaping mega spoon of bonus features, and it costs money for everybody but you. So just go to picmonkey.com/undisclosed. ​ ​ [00:55] Rabia Chaudry Hi, and welcome to the eighth episode of Undisclosed: The State v. ​ ​ Adnan Syed. My name’s Rabia Chaudry. I’m an attorney and national security fellow, and I blog ​ at SplitTheMoon.com. I’m joined with my colleagues Colin Miller, who is an associate dean and professor at the University of South Carolina School of Law and is also the blog editor of the EvidenceProf blog. We’re also joined with Susan Simpson, who’s an associate with the Volkov ​ Law Group in D.C., and she blogs at The View from LL2. ​ ​ So, last time we discussed the key piece of evidence that the State of Maryland used to corroborate Jay’s story, and that evidence, as we all know, was the cell phone records. From what we understand, Adnan’s case was actually the first of its kind in Maryland.
    [Show full text]
  • Imessage Privacy HITB, Kuala Lumpur, Oct
    Quarkslab on iMessage Privacy HITB, Kuala Lumpur, oct. 2013 @pod2g ([email protected]) gg ([email protected]) Presentations • Quarkslab is a research company specialized in cutting edge solutions to complex security problems. We provide innovative, efficient and practical solutions based on profound knowledge and years of experience in the field. • gg: security researcher, cryptography R.E. specialist. Joined Quarkslab in 2012 • @pod2g: security researcher, long background in Apple product security. Joined Quarkslab in 2013 Plan I. The current political and media context II. The iMessage protocol III. MITM attacks IV. Countermeasures V. Final thoughts I. THE CONTEXT NSA, PRISM, Apple NSA’s PRISM (US-984XN) • American supervision program • Mass surveillance data mining • Based on alliances with american firms • Can collect texts, emails, photos, etc. • Foreigners are also potential targets • Program was leaked by Edward Snowden Is Apple included? • Washington Post have leaked PRISM presentation slides that are said to be coming from the NSA • Looking at them, Apple joined in oct 2012 • Slides talk of « data collection », which sounds like a transparent process Apple publicly says: « Two weeks ago, when technology companies were accused of indiscriminately sharing customer data with government agencies, Apple issued a clear response: We first heard of the government’s “Prism” program when news organizations asked us about it on June 6. We do not provide any government agency with direct access to our servers, and any government agency requesting customer content must get a court order. » Source: https://www.apple.com/apples-commitment-to-customer-privacy/ What about iMessages? « Apple has always placed a priority on protecting our customers’ personal data, and we don’t collect or maintain a mountain of personal details about our customers in the first place.
    [Show full text]
  • ABF Podcast Series and Communication and Media
    Document 1 ABF Podcast Series A monthly podcast series featuring different elements of Australian Border Force will be developed. The series will invite engagement with ABF by the Australian public and related government agencies, promote ABF’s border security arrangements and position ABF as a policy champion. The podcast series will be developed in-house and distributed via a number of suitable podcast directories and the Border.gov.au website. The series could be promoted through LinkedIn, Twitter and Facebook engagement, Border Bulletin, and the revised DIBP intranet. Five reasons to podcast #1: Professional Development From Walkmans to iPods to smartphones, portable music has revolutionised the world, but in today’s society people are looking to take more than music with them–they’re looking for ways to learn more. Podcasts provide opportunities to learn without taking extra time in their day. #2: Trust Websites and blogs are a great way to give valuable information to your audience, but by delivering the same content through a podcast, you’re able to use your voice to bring your content to life. You have the ability to connect with your audience on a more personal level. #3: Mobility According to Eddison Research, nearly two-thirds of podcast consumers do most of their podcast listening on mobile devices. With a website or blog, you are asking an audience to sit down and give you 10 – 15 minutes of their time to read your posts. By turning that same material into a podcast, you’ve opened up your audience from people sitting down at their desk to people in the car, jogging, and working.
    [Show full text]
  • Diseño E Implementación De Actualizaciones Over the Air (OTA) Para Redes De Sensores Inalámbricas
    Diseño e implementación de actualizaciones Over The Air (OTA) para redes de sensores inalámbricas David García Fernández GRADO EN INGENIERÍA INFORMÁTICA FACULTAD DE INFORMÁTICA UNIVERSIDAD COMPLUTENSE DE MADRID Trabajo Fin de Grado en Ingeniería Informática Curso 2018-2019 Director: Joaquín Recas Resumen en castellano El objeto de este trabajo es el estudio de la viabilidad de las actualizaciones de firmware Over The Air (OTA) utilizando una red LPWAN, en concreto LoRaWAN. Dar soporte para actualizaciones de firmware OTA a día de hoy resulta fundamental y más todavía cuando estos nodos se encuentran en lugares remotos o sitios donde el acceso es muy limitado o peligroso. Tener implementada la funcionalidad para actualizaciones vía OTA permite corregir errores o añadir nuevas funcionalidades a distancia. Uno de los objetivos prioritarios consiste en que la misma actualización pueda llegar a un conjunto de nodos a la vez evitando tener que actualizar los nodos uno por uno, ya que esto supondría el envío de gran cantidad de información duplicada. Para llevar a cabo esta tarea, se ha realizado un estudio en profundidad sobre las características y el funcionamiento de la red LoRaWAN teniendo en cuenta que las redes LPWAN en general dificultan llevar a cabo este tipo de actualizaciones debido a sus conocidas limitaciones en cuanto a tamaño de payload y elevada latencia. Finalmente, este trabajo demuestra la viabilidad de las OTA mediante la aplicación de parches de actualización de firmware a conjuntos de nodos. Palabras clave OTA Over The Air Pycom Lopy STM32L475 LoRa LoRaWAN Bajo consumo Firmware OTA LoRa Server Red de sensores Abstract The aim of this work is the study of the feasibility of firmware updates Over The Air (OTA) using an LPWAN network, specifically LoRaWAN.
    [Show full text]
  • Blogging for Engines
    BLOGGING FOR ENGINES Blogs under the Influence of Software-Engine Relations Name: Anne Helmond Student number: 0449458 E-mail: [email protected] Blog: http://www.annehelmond.nl Date: January 28, 2008 Supervisor: Geert Lovink Secondary reader: Richard Rogers Institution: University of Amsterdam Department: Media Studies (New Media) Keywords Blog Software, Blog Engines, Blogosphere, Software Studies, WordPress Summary This thesis proposes to add the study of software-engine relations to the emerging field of software studies, which may open up a new avenue in the field by accounting for the increasing entanglement of the engines with software thus further shaping the field. The increasingly symbiotic relationship between the blogger, blog software and blog engines needs to be addressed in order to be able to describe a current account of blogging. The daily blogging routine shows that it is undesirable to exclude the engines from research on the phenomenon of blogs. The practice of blogging cannot be isolated from the software blogs are created with and the engines that index blogs and construct a searchable blogosphere. The software-engine relations should be studied together as they are co-constructed. In order to describe the software-engine relations the most prevailing standalone blog software, WordPress, has been used for a period of over seventeen months. By looking into the underlying standards and protocols of the canonical features of the blog it becomes clear how the blog software disperses and syndicates the blog and connects it to the engines. Blog standards have also enable the engines to construct a blogosphere in which the bloggers are subject to a software-engine regime.
    [Show full text]
  • Structured Feedback
    Structured Feedback A Distributed Protocol for Feedback and Patches on the Web of Data ∗ Natanael Arndt Kurt Junghanns Roy Meissner Philipp Frischmuth Norman Radtke Marvin Frommhold Michael Martin Agile Knowledge Engineering and Semantic Web (AKSW) Institute of Computer Science Leipzig University Augustusplatz 10 04109 Leipzig, Germany {arndt|kjunghanns|meissner|frischmuth|radtke|frommhold|martin}@informatik.uni-leipzig.de ABSTRACT through web resources. With the advent of discussion fo- The World Wide Web is an infrastructure to publish and re- rums, blogs, short message services like Twitter and on- trieve information through web resources. It evolved from a line social networks like Facebook, the web evolved towards static Web 1.0 to a multimodal and interactive communica- the Web 2.0. With the Semantic Web resp. Web of Data, tion and information space which is used to collaboratively the web is now evolving towards a Web 3.0 consisting of contribute and discuss web resources, which is better known structured and linked data resources (Linked Data, cf. [3]). as Web 2.0. The evolution into a Semantic Web (Web 3.0) Even though Web 2.0 services can be transformed to pro- proceeds. One of its remarkable advantages is the decentral- vide Linked Data [7], there is a need for services to collabo- ized and interlinked data composition. Hence, in contrast ratively interact with meaningful data and enable (Linked) to its data distribution, workflows and technologies for de- Data Services to be integrated into the existing social web centralized collaborative contribution are missing. In this stack. Currently the Distributed Semantic Social Network paper we propose the Structured Feedback protocol as an (DSSN, section 3.1 and [18]) is available as a framework interactive addition to the Web of Data.
    [Show full text]
  • Cobra: Content-Based Filtering and Aggregation of Blogs and RSS Feeds
    Cobra: Content-based Filtering and Aggregation of Blogs and RSS Feeds Ian Rose, Rohan Murty, Peter Pietzuch, Jonathan Ledlie, Mema Roussopoulos, and Matt Welsh School of Engineering and Applied Sciences { Harvard University } ianrose,rohan,prp,jonathan,mema,mdw @eecs.harvard.edu Abstract suited to tracking and indexing such rapidly-changing Blogs and RSS feeds are becoming increasingly popular. The content. Many users make use of RSS feeds, which in blogging site LiveJournal has over 11 million user accounts, conjunction with an appropriate reader, allow users to re- and according to one report, over 1.6 million postings are made to blogs every day. The “Blogosphere” is a new hotbed of ceive rapid updates to sites of interest. However, existing Internet-based media that represents a shift from mostly static RSS protocols require each client to periodically poll to content to dynamic, continuously-updated discussions. The receive new updates. In addition, a conventional RSS problem is that finding and tracking blogs with interesting con- tent is an extremely cumbersome process. feed only covers an individual site, such as a blog. The In this paper, we present Cobra (Content-Based RSS Ag- current approach used by many users is to rely on RSS gregator), a system that crawls, filters, and aggregates vast aggregators, such as SharpReader and FeedDemon, that numbers of RSS feeds, delivering to each user a personalized collect stories from multiple sites along thematic lines feed based on their interests. Cobra consists of a three-tiered (e.g., news or sports). network of crawlers that scan web feeds, filters that match Our vision is to provide users with the ability to per- crawled articles to user subscriptions, and reflectors that pro- form content-based filtering and aggregation across mil- vide recently-matching articles on each subscription as an RSS feed, which can be browsed using a standard RSS reader.
    [Show full text]