Thin Client Development and Wireless Markup Languages
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Smashing Ebook
IMPRINT Imprint © 2014 Smashing Magazine GmbH, Freiburg, Germany ISBN (PDF): 978-3-94454087-0 Cover Design: Veerle Pieters eBook Strategy and Editing: Vitaly Friedman Technical Editing: Cosima Mielke Planning and Quality Control: Vitaly Friedman, Iris Lješnjanin Tools: Elja Friedman Syntax Highlighting: Prism by Lea Verou Idea & Concept: Smashing Magazine GmbH 2 About This Book Slow loading times break the user experience of any web- site—no matter how well crafted it might be. In fact, it only takes three seconds until users lose their interest in a site if they don’t get a response immediately. If another site happens to be 250ms faster than yours, then users are more inclined to switch to a competitor’s website in no time. Web fonts, heavy JavaScript, third-party widgets — all of them can sum up to become a real performance bot- tleneck. Nevertheless, tracking that down does not only improve loading times but also results in a much snappi- er experience and a higher user engagement. In this eBook, we’ve compiled an entire selection of front-end and server-side techniques that will help you tackle such bottlenecks. Find out how to speed up exist- ing websites, build high-performance sites (for both mo- bile and desktop), and prepare them for heavy-load situa- tions. Furthermore, you’ll learn more about how perfor- mance improvements and a 97–99 Google PageSpeed score were achieved on Smashing Magazine, as well as how optimization strategies can enhance real-life projects by taking a closer look at Pinterest’s paint performance case study. -
WURFL and WALL
DDR Workshop WURFL, WALL and the community of mobile developers Luca Passani Solutions Architect [email protected] Device Fragmentation is deeper than Standards Can Reach Same mark-up, Same business logic, same device manufacturer,yet... you need to build two applications © 2006 Openwave Systems Inc. 2 Device Fragmentation is not only about standards Show me a standard that can turn one application into the other automatically (or just theoretically!) and I will be very impressed! © 2006 Openwave Systems Inc. 3 WURFL and WALL © 2006 Openwave Systems Inc. 4 WURFL and WALL (1 of 2) WURFL and WALL address device fragmentation – Free tool for the Developer community – Open Source – http://wurfl.sourceforge.net – http://developer.openwave.com/dvl/tools_and_sdk/wurfl_and_wall / WURFL = Wireless Universal Resource FiLe – Repository of device capabilities maintained by the developer community – Open Source Middleware: Java, PHP, Perl and more – Popular with Content Providers, i.e. Model is validated by a large installed base. – Adopted by some operators too WALL = Wireless Abstraction Library – Builds on top of WURFL – JSP tag-library – HTML-like: produces WML, XHTML-MP and Compact-HTML – Simple to use and deploy. © 2006 Openwave Systems Inc. 5 WURFL and WALL (2 of 2) WURFL Core Team: – Luca Passani: Openwave Consultant. – Andrea Trasatti: Independent Extended Team: – Between 40 and 200 (varying degrees of effort) – Hundreds of enthusiastic users around the world! The Community!!! – 2000+ strong developer mailing list (WMLProgramming on Yahoo groups) – Core Team has high credibility with the developer community. – The result of years of work helping mobile developers. © 2006 Openwave Systems Inc. 6 WURFL and WALL: Under the Hood ( I) • Driving Concept from the beginning of the WURFL project: “Essential device information MUST be publicly available ” • XML File containing device profiles • Comprehensive Device Repository – 7000+ devices (including firmware subversions of the same device) • Device profile is a list of capabilities (AKA attributes) and values. -
ABBREVIATIONS EBU Technical Review
ABBREVIATIONS EBU Technical Review AbbreviationsLast updated: January 2012 720i 720 lines, interlaced scan ACATS Advisory Committee on Advanced Television 720p/50 High-definition progressively-scanned TV format Systems (USA) of 1280 x 720 pixels at 50 frames per second ACELP (MPEG-4) A Code-Excited Linear Prediction 1080i/25 High-definition interlaced TV format of ACK ACKnowledgement 1920 x 1080 pixels at 25 frames per second, i.e. ACLR Adjacent Channel Leakage Ratio 50 fields (half frames) every second ACM Adaptive Coding and Modulation 1080p/25 High-definition progressively-scanned TV format ACS Adjacent Channel Selectivity of 1920 x 1080 pixels at 25 frames per second ACT Association of Commercial Television in 1080p/50 High-definition progressively-scanned TV format Europe of 1920 x 1080 pixels at 50 frames per second http://www.acte.be 1080p/60 High-definition progressively-scanned TV format ACTS Advanced Communications Technologies and of 1920 x 1080 pixels at 60 frames per second Services AD Analogue-to-Digital AD Anno Domini (after the birth of Jesus of Nazareth) 21CN BT’s 21st Century Network AD Approved Document 2k COFDM transmission mode with around 2000 AD Audio Description carriers ADC Analogue-to-Digital Converter 3DTV 3-Dimension Television ADIP ADress In Pre-groove 3G 3rd Generation mobile communications ADM (ATM) Add/Drop Multiplexer 4G 4th Generation mobile communications ADPCM Adaptive Differential Pulse Code Modulation 3GPP 3rd Generation Partnership Project ADR Automatic Dialogue Replacement 3GPP2 3rd Generation Partnership -
Open Orchestra Release 1.0.3
Open Orchestra Release 1.0.3 July 04, 2016 Changelogs 1 Indices and tables 3 i ii Open Orchestra, Release 1.0.3 The main documentation is organized into a couple sections: • Changelogs • Introduction • User guide • Developer guide • Hosting guide • Miscellaneous Changelogs 1 Open Orchestra, Release 1.0.3 2 Changelogs CHAPTER 1 Indices and tables • genindex • modindex • search 1.1 Versions 1.x.x 1.1.1 1.0.x CHANGELOG for 1.0.5 Url to see changes: • Cms bundle • Display bundle • Model bundle • Model interface • Front bundle • Base bundle • Base api bundle • Base api model bundle • Media bundle • User bundle • Theme bundle • Worflow function bundle • Orchestra libs • Media admin bundle 3 Open Orchestra, Release 1.0.3 Bug fixes • [open-orchestra-cms-bundle] Change the appConfigurationView creation order #1762( juchi) CHANGELOG for 1.0.4 Url to see changes: • Cms bundle • Display bundle • Model bundle • Model interface • Front bundle • Base bundle • Base api bundle • Base api model bundle • Media bundle • User bundle • Theme bundle • Worflow function bundle • Orchestra libs • Media admin bundle Configuration changes • Update requirement symfony to symfony/symfony" : "~2.7.4" #80 • Update requirement twig to twig/twig": "~1.23.0 #80 Bug fixes • Fix dependency doctrine/mongodb-odm-bundle #182 • Fix type nodeId in php doc of NodeInterface and ReadNodeInterface #177 CHANGELOG for 1.0.3 Url to see changes: • Cms bundle • Display bundle • Model bundle • Model interface 4 Chapter 1. Indices and tables Open Orchestra, Release 1.0.3 • Front bundle • Base -
XML for Java Developers G22.3033-002 Course Roadmap
XML for Java Developers G22.3033-002 Session 1 - Main Theme Markup Language Technologies (Part I) Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Course Roadmap Consider the Spectrum of Applications Architectures Distributed vs. Decentralized Apps + Thick vs. Thin Clients J2EE for eCommerce vs. J2EE/Web Services, JXTA, etc. Learn Specific XML/Java “Patterns” Used for Data/Content Presentation, Data Exchange, and Application Configuration Cover XML/Java Technologies According to their Use in the Various Phases of the Application Development Lifecycle (i.e., Discovery, Design, Development, Deployment, Administration) e.g., Modeling, Configuration Management, Processing, Rendering, Querying, Secure Messaging, etc. Develop XML Applications as Assemblies of Reusable XML- Based Services (Applications of XML + Java Applications) 2 1 Agenda XML Generics Course Logistics, Structure and Objectives History of Meta-Markup Languages XML Applications: Markup Languages XML Information Modeling Applications XML-Based Architectures XML and Java XML Development Tools Summary Class Project Readings Assignment #1a 3 Part I Introduction 4 2 XML Generics XML means eXtensible Markup Language XML expresses the structure of information (i.e., document content) separately from its presentation XSL style sheets are used to convert documents to a presentation format that can be processed by a target presentation device (e.g., HTML in the case of legacy browsers) Need a -
Wireless Application Protocol WAP
Wireless Application Protocol WAP F. Ricci 2008/2009 Content Web and mobility Problems of HTML in the mobile context Wap 1.x Motivations Features Architecture Examples of WML (Wireless Markup Language) pages Wap 2.0 XHTML MP Examples Differences with Wap 1.x Examples World Wide Web and mobility Protocol (HTTP, Hypertext Transfer Protocol) and language (HTML, Hypertext Markup Language) of the Web have not been designed for mobile applications and mobile devices, thus creating many problems! Typical transfer sizes HTTP request: 100-350 byte responses avg. <10 kbyte, header 160 byte, GIF 4.1kByte, JPEG 12.8 kbyte, HTML 5.6 kbyte but also many large files that cannot be ignored The Web is not a file system Web pages are not simple files to download static and dynamic content, interaction with servers via forms, content transformation, push technologies etc. many hyperlinks, automatic loading and reloading, redirecting a single click might have big consequences! HTML and mobile devices HTML designed for computers with “high” performance, color high-resolution display, mouse, hard disk typically, web pages optimized for design, not for communication Mobile devices often only small, low-resolution displays, very limited input interfaces (small touch-pads, soft-keyboards) Additional “features” animated GIF, Java AWT, Frames, ActiveX Controls, Shockwave, movie clips, audio, ... many web pages assume true color, multimedia support, high-resolution and many plug-ins Web pages ignore the heterogeneity of end-systems! -
Matml: XML for Information Exchange with Materials Property Data
MatML: XML for Information Exchange with Materials Property Data Aparna S. Varde1,2 Edwin F. Begley Sally Fahrenholz-Mann 1. Department of Computer Science Computer Integrated Building Electronic Publishing and Content 2. Materials Science Program Processes Group Management Worcester Polytechnic Institute (WPI) National Institute of Standards and ASM International Worcester, MA, USA Technology (NIST) Materials Park, OH, USA [email protected] Gaithersburg, MD, USA sally.fahrenholz- [email protected] [email protected] ABSTRACT 1. INTRODUCTION This paper describes the development and use of MatML, the XML, the eXtensible Markup Language is today a widely Materials Markup Language. MatML is an emerging XML accepted standard for storage and exchange of information. It standard intended primarily for the exchange of materials serves a twofold purpose of providing a data model for storing property information. It provides a medium of communication for information and a medium of communication for exchanging users in materials science and related fields such as manufacturing information over the worldwide web [29]. and aerospace. It sets the stage for the development of semantic Domain-specific markup languages are often defined within the web standards to enhance knowledge discovery in materials context of XML to serve as the means for storing and exchanging science and related areas. MatML has been used in applications information in the respective domains. Some examples of such such as the development of materials digital libraries and analysis markup languages include [14, 9]: of contaminant emissions data. Data mining applications of MatML include statistical process control and failure analysis. • AniML: Analytical Information Markup Language Challenges in promoting MatML involve satisfying a broad range • ChemML: Chemical Markup Language of constituencies in the international engineering and materials science community and also adhering to other related standards in • femML: Finite Element Modeling Markup Language web data exchange. -
Guia Internet Para Periodistas.Pdf
Indice general Presentación ................................................................................................................................... 9 Introducción ................................................................................................................................. 11 Capítulo 1. Sociedad de la información e Internet. Isabel Fernández Morales ......................... 13 1.1 Sociedad de la información .................................................................................................. 13 1.2 Historia de Internet .............................................................................................................. 15 1.3 Tecnologías de acceso .......................................................................................................... 18 1.4 Tipo de acceso ..................................................................................................................... 18 1.5 Terminales de acceso ........................................................................................................... 20 1.6 Servidores ............................................................................................................................. 20 1.6.1 Servicios de web hosting ............................................................................................... 21 1.7 Proveedores de acceso ......................................................................................................... 22 1.8 Dominios ............................................................................................................................. -
Forcepoint DLP Supported File Formats and Size Limits
Forcepoint DLP Supported File Formats and Size Limits Supported File Formats and Size Limits | Forcepoint DLP | v8.8.1 This article provides a list of the file formats that can be analyzed by Forcepoint DLP, file formats from which content and meta data can be extracted, and the file size limits for network, endpoint, and discovery functions. See: ● Supported File Formats ● File Size Limits © 2021 Forcepoint LLC Supported File Formats Supported File Formats and Size Limits | Forcepoint DLP | v8.8.1 The following tables lists the file formats supported by Forcepoint DLP. File formats are in alphabetical order by format group. ● Archive For mats, page 3 ● Backup Formats, page 7 ● Business Intelligence (BI) and Analysis Formats, page 8 ● Computer-Aided Design Formats, page 9 ● Cryptography Formats, page 12 ● Database Formats, page 14 ● Desktop publishing formats, page 16 ● eBook/Audio book formats, page 17 ● Executable formats, page 18 ● Font formats, page 20 ● Graphics formats - general, page 21 ● Graphics formats - vector graphics, page 26 ● Library formats, page 29 ● Log formats, page 30 ● Mail formats, page 31 ● Multimedia formats, page 32 ● Object formats, page 37 ● Presentation formats, page 38 ● Project management formats, page 40 ● Spreadsheet formats, page 41 ● Text and markup formats, page 43 ● Word processing formats, page 45 ● Miscellaneous formats, page 53 Supported file formats are added and updated frequently. Key to support tables Symbol Description Y The format is supported N The format is not supported P Partial metadata -
Understanding
Implementing UBL Mark Crawford UBL Vice Chair XML 2003 9 December 2003 Why Are We Talking About UBL • UBL fulfils the promise of XML for business by defining a standard cross-industry vocabulary • UBL is the ebXML missing link • UBL plus ebXML enables the next generation of eBusiness exchanges – Cheaper, easier, Internet-ready – Extends benefits of EDI to small businesses – Fits existing legal and trade concepts – Allows re-use of data • UBL can provide the XML payload for a wide variety of other web-based business frameworks Overview 1 What and Why of UBL 2 The Design of UBL ebXML Core Components Naming and Design Rules Document Engineering Customizing UBL 3 The Content of UBL 1.0 What is Normative What is non-Normative Availability 4 Making UBL Happen 5 UBL Phase 2 6 Summary The promise of XML for e-business • Plug ‘n’ play electronic commerce – Spontaneous trade – No custom programming • Ubiquity on the Internet – Dirt-cheap tools – Complete platform independence – Enable true global market availability • Enable universal interoperability – Abandon existing EDI systems – Handle both "publication" document types and "transactional" documents Goals for Successful eBusiness Services • Web-enable existing fax- and paper-based business practices • Allow businesses to upgrade at their own pace • Preserve the existing investment in electronic business exchanges • Integrate small and medium-size businesses into existing electronic data exchange-based supply chains The standardization of XML business documents is the easiest way to accomplish -
Wap, Xhtml and Android
WAP, XHTML AND ANDROID Jaume Barceló University Carlos III of Madrid Antonio de la Oliva Ruben cuevas Service Engineering Laboratory Ignacio soto BACK IN 1999, • Mobile and Internet communications were separate worlds • Nokia 7110, first mobile phone with a WAP browser. • WAP: Wireless Application Protocol. • Extra-simplified access to the Internet, due to terminal limitations and limited available bandwidth. SMALL LIMITATIONS, • Extremely limited bandwidth • SMS • Circuit-switching • Wait-and-pay • A substantial increase thanks to GPRS (2.5G) ~ 56kbps • Memory and processor limitations • Low resolution monochrome screen • No mouse, 15-keys keyboard WAP PROTOCOL STACK Internet Protocol Stack HTML Wireless Application Environment (WAE) JavaScript 1. Wireless Session Layer (WSP) HTTP 2. Wireless Transaction Protocol (WTP) TLS-SSL 3. Wireless Transport Layer Security (WTLS) 4. Wireless Datagram Protocol (WDP) TCP/IP UDP/IP Bearers: SMS USSD CSD CDMA IS-136 CDPD Etc.. A GW WAS REQUIRED WIRELESS APPLICATION ENVIRONMENT In WAP 1.X Wireless Markup Language (WML) Relies on a card/desk paradigm WMLScript WML EXAMPLE <?xml version="1.0"?> <!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml"> <wml> <card id="card1" title="Tutorial"> <do type="accept" label="Answer"> <go href="#card2"/> </do> <p><select name="name"> <option value="HTML">HTML Tutorial</option> <option value="XML">XML Tutorial</option> <option value="WAP">WAP Tutorial</option> </select></p> </card> <card id="card2" title="Answer"> <p>You -
Chapter 11 Mobile
Overview • Web and Mobility • HTTP and HTML Chapter 11 • Mobile Web Architectures Mobile Web • Wireless Application Protocol WAP •WML •WMLScript •WTAI Distributed Mobile Computing Computing Group Summer 2002 Distributed Computing Group MOBILE COMPUTING R. Wattenhofer 11/2 World Wide Web and Mobility WWW example • Request to port 80 • Protocol (HTTP, Hypertext Transfer Protocol) and language GET/HTTP/1.0 (HTML, Hypertext Markup Language) of the Web have not been • Response from server designed for mobile applications and mobile devices. HTTP/1.1 200 OK Date: Fri, 20 Jun 2002 14:52:12 GMT • Typical transfer sizes Server: Apache/1.3.26 – HTTP request: 100-350 byte Connection: close – responses avg. <10 kbyte, header 160 byte, GIF 4.1kByte, JPEG Content-Type: text/html 12.8 kbyte, HTML 5.6 kbyte <html> <head> <title>Distributed Computing Group</title> <meta http-equiv="Content-Type" content="text/html; – but also many large files that cannot be ignored charset=iso-8859-1"> <link rel=stylesheet href="styles.css" type="text/css"> </head> <body • The Web is no file system bgcolor="#FFFFFF" text="#000000" link="#0000A0" – Web pages are not simple files to download vlink="#0000A0" alink="#00A000"> <p align="right" style="margin-bottom:0px"> <a – static and dynamic content, interaction with servers via forms, href="index.html"><img border="0" height="117" content transformation, push technologies etc. width="429" src="pics/dcg.gif" alt="Distributed Computing Group"></a> </p> – many hyperlinks, automatic loading and reloading, redirecting <hr size="1" noshade> – a single click might have big consequences! <h1>Distributed Computing Group</h1> <p class="topic"> … Distributed Computing Group MOBILE COMPUTING R.