SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Message Management

kim avatar
kim
8 diapositives · 216 Views · Sep 13, 2014

This document presents an exploration of messaging systems and their application in computing, specifically focusing on the Message-based Model-View-Controller (M-MVC) architecture and the NaradaBrokering messaging system. It emphasizes the trade-offs in performance, concurrency, and programming ease when using explicit messaging components. The paper outlines various communication patterns, the performance models for scientific applications, and the integration of desktop and web services. It proposes a framework that simplifies collaboration across diverse clients, highlighting practical examples such as SVG Browser and OpenOffice.

Message Management - slide 1
01 / 8Message Management
1 / 17

Télécharger la présentation

Message Management
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. Message Management April 27 2006 Geoffrey Fox Computer Science, Informatics, Physics Pervasive Technology Laboratories Indiana University Bloomington IN 47401 gcf@indiana.edu http://www.infomall.org

  2. Messaging Runtime I • Components communicate via messages • MPI • SOAP • Putting bytes on a stack • Events/Interrupts • Between Services, Peers (of P2P), CCA Components, Objects, Procedures, Handlers • Trade-offs in performance, concurrency, ease of programming depend on how explicit message is • Hard/impossible to convert conventional programs efficiently into explicit message linked components • Similar implicit (and unnecessary) side-effects make concurrency hard • Message-based MVC makes Model and View components • CCR is an example of a language that can exploit messaging between threads • It is applied to Robotics which typically uses dataflow as in Khoros (image processing)

  3. Messaging Runtime II • We built NaradaBrokering messaging system applied to distributed (Grid, P2P, Web service) and desktop applications • Initially we will establish performance expectations • Such as MPI has overhead of a few microseconds • Nearby distributed systems have overheads of 1-2 milliseconds • Thread Scheduling overhead is around 10 milliseconds (Java, XP) • CCR is better • What are primitives needed for communication (MPI and CCR collectives) • Interaction between otherwise independent threads due to Cache conflicts • We understand both communication patterns and performance models for scientific applications

  4. Web Services and M-MVC • Web Services are naturally M-MVC – Message based Model View Controller with • Model is Component • Controller is Messages (NaradaBrokering) • View is rendering As Controller

  5. Desktop and Web Services with MMVC • Most desktop applications are in fact roughly MVC with controller formed by “system interrupts” with View and Model communicating by “post an event” and define a “listener” programming mode • We propose to integrate desktop and Web Service approach by systematic use of MMVC and NaradaBrokering • Allows easier porting to diverse clients and automatic collaboration • Attractive for next generation of Linux desktop clients • We have demonstrated for SVG Browser (Scalable Vector Graphics), OpenOffice and PowerPoint • “Glob” programming style makes hard

  6. Events Per 0.5 ms NB on RipvanwinkleNB on ViewNB on Model Mean ms Mean Mouseup Mean Mousemove Mean Mousedown 15 runs each split over 3 days

  7. SM-MV Collaboration Shared Output portSingle Model, Multiple View SM-MV CollaborativeWeb Service XGSPSession Control

  8. MM-MV Collaboration Shared Input portMultiple Model, Multiple View MM-MV Collaborative Web Service