1 / 10

WiDeX Problem Statement

The WiDeX initiative, discussed at IETF 63 in Paris, focuses on enhancing Remote User Interface (UI) technologies. It aims to create an open, platform-independent protocol for IP-based networks to handle initialization, updates, and event management for user-visible objects. Challenges include UI description standardization, session initiation, synchronization, and security concerns. WiDeX proposes a modular architecture while leveraging existing protocols. By addressing these issues, WiDeX seeks to support a diverse range of devices and user interfaces, improving connectivity and user experiences.

vesta
Télécharger la présentation

WiDeX Problem Statement

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WiDeX Problem Statement Dean Willis <dean.willis@softarmor.com> Vlad Stirbu <vlad.stirbu@nokia.com> RUI BoF, IETF 63, Paris August 2nd , 2005 1 IETF 63, Remote UI BoF

  2. What is Remote UI? • A mechanism that enables user interfaces to be rendered on other devices than those that have the application logic. Remote UI Server Remote UI Client UI Semantics Application logic Processed Input Information 2 IETF63, Remote UI BoF

  3. Remote UI Alternatives Now • Framebuffer-level – VNC, RDP, Hot Desk • Server framebuffer is copied across the network to a framebuffer on the client • Graphics-level – X Windows • Drawing request to the graphical device interface (GDI) copied across the network • The client is interpreting these commands and renders in its framebuffer 3 IETF63, Remote UI BoF

  4. Ecosystem: Devices 4 IETF63, Remote UI BoF

  5. Ecosystem: User Interfaces 5 IETF63, Remote UI BoF

  6. Highly Diverse Ecosystem • Physical characteristics • screen size and ratio • color depth • User Interface characteristics • windowing system and widget sets • input methods 6 IETF63, Remote UI BoF

  7. Challenges • How to describe the user interface in terms of widgets? • How to find matches between UI servers and clients? • How to start UI remoting sessions? • How to keep the UI synchronised? Out of Scope 7 IETF63, Remote UI BoF

  8. Some Answers • UI descriptions • W3C markup languages: XHTML, XHTML + SVG, etc. • Discovery session setup • IETF: MMUSIC, ZeroConf 8 IETF63, Remote UI BoF

  9. WiDeX Goal & Scope • Specify an open, platform-independent method for use in an IP-basednetwork to convey initialisation, update and eventing information aboutuser-visible objects, i.e. widgets. • Network “plumbing” • Connectivity. e.g. NATs, firewalls • Security • Reliability • UI remoting management • URI definition • Session-Transaction model • Synchronisation • Events 9 IETF63, Remote UI BoF

  10. WiDeX Requirements & Assumptions • Protocol must have a modular architecture • UI semantic independent • Discovery and session setup mechanism independent • Privacy concerns must be addressed, e.g. P3P • Protocol must support server initiated updates • Full screen updates • Incremental updates • Protocol must support client initiated updates • The protocol must have support for authentication and secure sessions • Existing protocols should be reused when appropriate 10 IETF63, Remote UI BoF

More Related