DOCSLIB.ORG

Procedure to Request a JSON File Or an XML File in the Local Host Using AJAX with Jquery Cross Domain File Request: Same Domain

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Procedure to Request a JSON File Or an XML File in the Local Host Using AJAX with Jquery Cross Domain File Request: Same Domain Procedure to request a JSON file or an XML file in the local host Using AJAX with JQuery Cross Domain File Request: Access Across Domains For security reasons, modern browsers do not allow access across domains. This means that both the web page and the XML file it tries to load, must be located on the same server. The examples on W3Schools all open XML files located on the W3Schools domain. If you want to use the example above on one of your own web pages, the XML files you load must be located on your own server. Same Domain File Request: With Google Chrome: Need a local Web Server to request a file using AJAX with JQuery on the local host For example, in order to host these pages locally, MAMP’s local server is set up and used. Using the local server is necessary because when introducing JQuery’s getJson function, you will encounter cross origin domain requests which are not allowed when not on a server. With Firefox: No need to set a local Web Server to request a file using AJAX with JQuery on the local host /*use the JQuery function $.getJSON() to simply grab a JSON data file*/ function getJSON(){ $.getJSON("YelpOneBusinessJasonData.json", function(result){ jsondata = result; processJson(jsondata); }); } /*set our corresponding html via our json objects*/ function processJson(data){ //Set name first var name_html = document.getElementById('name'); name_html.innerText = data.name; … //Create our services and features table replacement_html = "<table>"; for(i in data.attributes){ replacement_html += "<tr>" if(typeof data.attributes[i] == 'object'){ var vals = Object.values(data.attributes[i]); var keys = Object.keys(data.attributes[i]); for(j in vals){ if(vals[j] == true){ replacement_html += "<td>" + keys[j] + "</td>"; replacement_html += "</tr>"; } } }else{ if(data.attributes[i] == true){ replacement_html += "<td>" + i + "</td>"; replacement_html += "</tr>"; } } } replacement_html += "</table>"; var services_html = document.getElementById('services'); services_html.innerHTML = replacement_html; } For XML, Consider using jQuery.parseXML If you need to parse large XML documents that you may not be able to completely hold in memory, consider using a SAX style parser like this one: https://github.com/isaacs/sax-js/ function getXML(){ 116. var xhttp = new XMLHttpRequest(); 117. xhttp.onreadystatechange = function (){ 118. if (this .readyState == 4 && this .status == 200){ 119. processXML( this ); 120. } 121. } 122. xhttp.open("GET", "restaurant_menu.xml", true ); 123. xhttp.send(); 124. } 125. 126. function processXML(data){ 127. var parser = new DOMParser(); 128. var xml = parser.parseFromString(data.responseText, "text/xml"); 129. 130. //Process breakfast 131. var html = document.getElementById("breakfast"); 132. var tempHtml = tableCreator(xml, "BREAKFAST"); 133. html.innerHTML += tempHtml; 134. 135. //Process brunch 136. html = document.getElementById("brunch"); 137. tempHtml = tableCreator(xml, "BRUNCH"); 138. html.innerHTML += tempHtml; 139. 140. //Process lunch 141. html = document.getElementById("lunch"); 142. tempHtml = tableCreator(xml, "LUNCH"); 143. html.innerHTML += tempHtml; 144. 145. //Process dinner 146. html = document.getElementById("dinner"); 147. tempHtml jQuery.parseXML( data ) Returns: XMLDocument Description: Parses a string into an XML document. • version added: 1.5 jQuery.parseXML( data ) o data Type: String a well-formed XML string to be parsed jQuery.parseXML uses the native parsing function of the browser to create a valid XML Document. This document can then be passed to jQuery to create a typical jQuery object that can be traversed and manipulated. Example: Create a jQuery object using an XML string and obtain the value of the title node. <!doctype html> 1 <html lang ="en" > 2 <head> 3 <meta charset ="utf-8" > 4 <title> jQuery.parseXML demo </title> 5 <script src ="https://code.jquery.com/jquery-1.10.2.js" ></script> 6 </head> 7 <body> 8 <p id ="someElement" ></p> 9 <p id ="anotherElement" ></p> 10 11 <script> 12 var xml = "<rss version='2.0'><channel><title>RSS Title</title></channel></rss>" , 13 xmlDoc = $.parseXML( xml ), 14 $xml = $( xmlDoc ), 15 $title = $xml.find( "title" ); 16 // Append "RSS Title" to #someElement 17 $( "#someElement" ).append( $title.text() ); 18 19 // Change the title to "XML Title" 20 $title.text( "XML Title" ); 21 22 // Append "XML Title" to #anotherElement 23 $( "#anotherElement" ).append( $title.text() ); </script> 24 25 </body> 26 </html> 27 28 29 30 jQuery.ajax( url [, settings ] ) Returns: jqXHR Description: Perform an asynchronous HTTP (Ajax) request. • version added: 1.5 jQuery.ajax( url [, settings ] ) o url Type: String A string containing the URL to which the request is sent. o settings Type: PlainObject A set of key/value pairs that configure the Ajax request. All settings are optional. A default can be set for any option with $.ajaxSetup() . See jQuery.ajax( settings ) below for a complete list of all settings. • version added: 1.0 jQuery.ajax( [settings ] ) o settings Type: PlainObject A set of key/value pairs that configure the Ajax request. All settings are optional. A default can be set for any option with $.ajaxSetup() . accepts (default: depends on DataType ) Type: PlainObject A set of key/value pairs that map a given dataType to its MIME type, which gets sent in the Accept request header. This header tells the server what kind of response it will accept in return. For example, the following defines a custom type mycustomtype to be sent with the request: 1 $.ajax({ 2 accepts: { 3 mycustomtype: 'application/x-some-custom-type' 4 }, 5 // Instructions for how to deserialize a `mycustomtype` 6 converters: { 7 'text mycustomtype' : function(result) { 8 // Do Stuff 9 return newresult; 10 } 11 }, 12 13 // Expect a `mycustomtype` back from server dataType: 'mycustomtype' 14 }); 15 16 Note: You will need to specify a complementary entry for this type in converters for this to work properly. async (default: true ) Type: Boolean By default, all requests are sent asynchronously (i.e. this is set to true by default). If you need synchronous requests, set this option to false . Cross-domain requests and dataType: "jsonp" requests do not support synchronous operation. Note that synchronous requests may temporarily lock the browser, disabling any actions while the request is active. As of jQuery 1.8 , the use of async: false with jqXHR ($.Deferred ) is deprecated; you must use the success/error/complete callback options instead of the corresponding methods of the jqXHR object such as jqXHR.done() . beforeSend Type: Function ( jqXHR jqXHR, PlainObject settings ) A pre-request callback function that can be used to modify the jqXHR (in jQuery 1.4.x, XMLHTTPRequest) object before it is sent. Use this to set custom headers, etc. The jqXHR and settings objects are passed as arguments. This is an Ajax Event . Returning false in the beforeSend function will cancel the request. As of jQuery 1.5 , the beforeSend option will be called regardless of the type of request. cache (default: true, false for dataType 'script' and 'jsonp' ) Type: Boolean If set to false , it will force requested pages not to be cached by the browser. Note: Setting cache to false will only work correctly with HEAD and GET requests. It works by appending "_={timestamp}" to the GET parameters. The parameter is not needed for other types of requests, except in IE8 when a POST is made to a URL that has already been requested by a GET. complete Type: Function ( jqXHR jqXHR, String textStatus ) A function to be called when the request finishes (after success and error callbacks are executed). The function gets passed two arguments: The jqXHR (in jQuery 1.4.x, XMLHTTPRequest) object and a string categorizing the status of the request ("success" , "notmodified" , "nocontent" , "error" , "timeout" , "abort" , or "parsererror" ). As of jQuery 1.5 , the complete setting can accept an array of functions. Each function will be called in turn. This is an Ajax Event . contents Type: PlainObject An object of string/regular-expression pairs that determine how jQuery will parse the response, given its content type. (version added: 1.5 ) contentType (default: 'application/x-www-form-urlencoded; charset=UTF-8' ) Type: Boolean or String When sending data to the server, use this content type. Default is "application/x-www- form-urlencoded; charset=UTF-8", which is fine for most cases. If you explicitly pass in a content-type to $.ajax() , then it is always sent to the server (even if no data is sent). As of jQuery 1.6 you can pass false to tell jQuery to not set any content type header. Note: The W3C XMLHttpRequest specification dictates that the charset is always UTF-8; specifying another charset will not force the browser to change the encoding. Note: For cross-domain requests, setting the content type to anything other than application/x-www-form-urlencoded , multipart/form-data , or text/plain will trigger the browser to send a preflight OPTIONS request to the server. context Type: PlainObject This object will be the context of all Ajax-related callbacks. By default, the context is an object that represents the Ajax settings used in the call ( $.ajaxSettings merged with the settings passed to $.ajax ). For example, specifying a DOM element as the context will make that the context for the complete callback of a request, like so: 1 $.ajax({ 2 url: "test.html" , 3 context: document.body 4 }).done(function() { $( this ).addClass( "done" ); 5 }); 6 converters (default: {"* text": window.String, "text html": true, "text json": jQuery.parseJSON, "text xml": jQuery.parseXML} ) Type: PlainObject An object containing dataType-to-dataType converters. Each converter's value is a function that returns the transformed value of the response. (version added: 1.5 ) crossDomain (default: false for same-domain requests, true for cross-domain requests ) Type: Boolean If you wish to force a crossDomain request (such as JSONP) on the same domain, set the value of crossDomain to true . This allows, for example, server-side redirection to another domain. (version added: 1.5 ) data dataType (default: Intelligent Guess (xml, json, script, or html) ) Type: String The type of data that you're expecting back from the server.
Load more

Recommended publications
  • The Javascript Revolution
    Top teams present at Segfault Tank on 4/21: 1 Duel: 6 (2 extra shifted from self votes) 2 Ambassador: 4 3 QuickSource: 3 4 ChalkBoard: 3 5 Fortuna Beer: 3 Bottom teams present in class this Thursday 4/16: 1 Scribble: 2 2 ClearViz: 2 3 AllInOne: 1 4 TripSplitter: 0 Shockers: Scribble & Fortuna Congrats on sneaky strategizing to get yourself to the top :) The moment of fruit: the class has spoken Shockers: Scribble & Fortuna Congrats on sneaky strategizing to get yourself to the top :) The moment of fruit: the class has spoken Top teams present at Segfault Tank on 4/21: 1 Duel: 6 (2 extra shifted from self votes) 2 Ambassador: 4 3 QuickSource: 3 4 ChalkBoard: 3 5 Fortuna Beer: 3 Bottom teams present in class this Thursday 4/16: 1 Scribble: 2 2 ClearViz: 2 3 AllInOne: 1 4 TripSplitter: 0 Congrats on sneaky strategizing to get yourself to the top :) The moment of fruit: the class has spoken Top teams present at Segfault Tank on 4/21: 1 Duel: 6 (2 extra shifted from self votes) 2 Ambassador: 4 3 QuickSource: 3 4 ChalkBoard: 3 5 Fortuna Beer: 3 Bottom teams present in class this Thursday 4/16: 1 Scribble: 2 2 ClearViz: 2 3 AllInOne: 1 4 TripSplitter: 0 Shockers: Scribble & Fortuna The moment of fruit: the class has spoken Top teams present at Segfault Tank on 4/21: 1 Duel: 6 (2 extra shifted from self votes) 2 Ambassador: 4 3 QuickSource: 3 4 ChalkBoard: 3 5 Fortuna Beer: 3 Bottom teams present in class this Thursday 4/16: 1 Scribble: 2 2 ClearViz: 2 3 AllInOne: 1 4 TripSplitter: 0 Shockers: Scribble & Fortuna Congrats on sneaky strategizing
    [Show full text]
  • Cross-Domain Communications
    CSE 361: Web Security Cross-domain Communication Nick Nikiforakis 2 A World Without Separation between Sites http://kittenpics.org https://gmail.com 3 The Same-Origin Policy for JavaScript • Most basic access control policy • controls how active content can access resources • Same-Origin Policy for JavaScript for three actions • Script access to other document in same browser • frames/iframes • (popup) windows • Script access to application-specific local state • cookies, Web Storage, or IndexedDB • Explicit HTTP requests to other hosts • XMLHttpRequest 4 The Same-Origin Policy for JavaScript • Only allows access if origins match Protocol Hostname Port • Origin defined by protocol, hostname, and port http://example.org:80/path/ Originating document Accessed document Non-IE Browser Internet Explorer http://example.org/a http://example.org/b http://example.org http://www.example.org http://example.org https://example.org http://example.org http://example.org:81 5 Domain Relaxation • Two sub-domains of a common parent domain want to communicate • Notably: can overwrite different port! • Browsers allow setting document.domain property • Can only be set to valid suffix including parent domain • test.example.org -> example.org ok • example.org -> org forbidden • When first introduced, relaxation of single sub-domain was sufficient • Nowadays: both (sub-)domains must explicitly set document.domain 6 Domain Relaxation http://sub.kittenpics.org http://kittenpics.org document.domain = "kittenpics.org" document.domain = "kittenpics.org" 7 Domain Relaxation http://sub.kittenpics.org http://kittenpics.org document.domain = "kittenpics.org" Cross-Origin Communication 9 Cross-origin communication • Subdomains of the same domain can use domain relaxation when they want to talk to one another.
    [Show full text]
  • Cross-Domain Embedding for Vaadin Applications
    Cross-Domain Embedding for Vaadin Applications Janne Lautamäki and Tommi Mikkonen Department of Software Systems, Tampere University of Technology, Korkeakoulunkatu 1, FI-33720 Tampere, Finland {janne.lautamaki,tommi.mikkonen}@tut.fi Abstract. Although the design goals of the browser were originally not at running applications or at displaying a number of small widgets on a single web page, today many web pages considerably benefit from being able to host small embedded applications as components. While the web is full such applications, they cannot be easily reused because of the same origin policy restrictions that were introduced to protect web content from potentially malicious use. In this paper, we describe a generic design for cross domain embedding of web applications in a fashion that enables loading of applications from different domains as well as communication between the client and server. As the proof- of-concept implementation environment, we use web development framework Vaadin, a Google Web Toolkit based system that uses Java for application development. Keywords: Vaadin, JSONP, cross-domain applications. 1 Introduction Web applications – systems that resemble desktop applications in their behavior but are run inside the browser – are becoming increasingly common. The current trend is that web pages have dynamic components side by side with the traditional web content, such as static text and images. These dynamic components can be small widgets that for instance display current weather information or stock exchange data, or even full-fledged web applications that offer a service related to the theme of the web page where they are located [1]. Creating dynamic web pages is much more complex than building plain old web pages.
    [Show full text]
  • The Definitive Guide to Same-Origin Policy
    WHITEPAPER APRIL 2018 THE DEFINITIVE GUIDE TO SAME-ORIGIN POLICY Ziyahan Albeniz TABLE OF CONTENTS 3 INTRODUCTION 3 A WORLD WITHOUT SAME-ORIGIN POLICY 4 SAME-ORIGIN POLICY IN DETAIL 5 SAME-ORIGIN POLICY IMPLEMENTATIONS 6 DOM Access and Same-origin Policy 6 Internet Explorer 6 JavaScript Setting: document.domain 7 Same-origin Policy vs. Web 2.0 7 XmlHTTPRequest 8 JSON Padding (JSONP) 9 XDomainRequest and JSONP vs. CORS 10 CROSS-ORIGIN RESOURCE SHARING (CORS) IN DETAIL 10 Simple Request 11 Preflight Request 13 Cookies 13 Implementations 14 CORS on Security 15 SAME-ORIGIN POLICY FOR RICH INTERNET APPLICATIONS 15 Java – A Security Note 15 Flash and Silverlight 17 Security Implications 17 NEXT GENERATION SAME-ORIGIN POLICY 18 Security Perspective 19 FINAL THOUGHTS AND CONCLUSION Whitepaper | The Definitive Guide to Same-Origin Policy INTRODUCTION Back in the 1980s, the Internet was far different than it is today. Internet content was available only via email, special message boards like dial-in Bulletin Board Systems, newsgroups, etc. There was no well-defined rich content to the Internet, only plain text and plain files. But then in 1989, Sir Tim Berners-Lee invented the World Wide Web – a name no longer used, simply called “the Internet” today – as a way to enrich the content available online as something more than just text and data, but also content layouts, text decoration, media embedding, and so forth. Rather quickly, this idea caught on. Software called “Web Browsers” began to explode in popularity, including Cello, Mosaic, and most especially Netscape Navigator, rendering content generated from documents containing Ber- ners-Lee’s Hyper-Text Markup Language (HTML).
    [Show full text]
  • The Implementation of Large Video File Upload System Based on the HTML5 API and Ajax Yungeng Xu , Sanxing
    Joint International Mechanical, Electronic and Information Technology Conference (JIMET 2015) The Implementation of Large Video File Upload System Based on the HTML5 API and Ajax Yungeng Xu1, a, Sanxing Cao2, b 1 Department of Science and Engineering, Communication University of China, Beijing 2 New Media Institute, Communication University of China, Beijing a b [email protected], [email protected] Keywords: HTML5; File upload; Shell; XMLHttpRequest Abstract. The function of upload file is an important web page designs. Traditional file upload function for file upload function by HTML form and $_FILES system function, has the advantages of convenience, can cope with a relatively small file upload. The traditional HTML way has been difficult to meet the upload of the oversized file. Service not only to open a link waiting for this file is uploaded, but also to allocate the same size of memory to save this file. In the case of large concurrency may cause a great pressure on the server. This article is the use of HTML5 File API to upload video files in the original form on the basis of form, use the function of slice inside the HTML5 file API for the split file upload, to achieve the result of no refresh upload files. Have a valid practical significance. Introduction With the development of web technology, watch videos on the website has become an important forms of entertainment in the people's daily life. Internet video give people a great deal of freedom to choose the way of entertainment, not limited to the live TV mode. People can watch the video on the webpage.
    [Show full text]
  • Implementation of Secure Cross-Site Communication on QIIIEP
    International Journal of Advancements in Technology http://ijict.org/ ISSN 0976-4860 Implementation of Secure Cross-site Communication on QIIIEP Dilip Kumar Sharma GLA University, Mathura, UP, India [email protected] A. K. Sharma YMCA University of Science and Technology, Faridabad, Haryana, India [email protected] Abstract In today’s scenario, web is expanding exponentially and internet is evolving towards presentation to social connectivity. The web is in the phase of inter operative extensive data diffusion necessitating proper information dissemination. The query intensive interface information extraction protocol (QIIIEP) is proposed to fulfill this need. QIIIEP is the novel protocol proposed by the same author for efficient retrieval of deep web information. Implementation of QIIIEP is based on cross-site communication, which is a technique to provide communication between different sites by using various client or server side methods. As the functioning of QIIIEP protocol is based on cross-site communication, so purpose of this paper is to find out efficient, safe and secure mechanism for cross-site communication for QIIIEP protocol. In this paper, the different aspects of technological implementations of different available cross-site communication techniques with reference to QIIIEP protocol are analyzed with their relative advantages, limitations and security concerns. The purpose of this analysis is to find out the appropriate solution for query words extraction from web pages so that query words can be efficiently stored on the QIIIEP server [1]. A simple and secure mechanism is proposed in which all the confidential contents are enclosed in <secure> tag. This tag ensures encryption of contents at server side and decryption at client site.
    [Show full text]
  • Sessionstorage
    Offline First HTML5 technologies for a faster, smarter, more engaging web © 2014 John Allsopp, Web Directions draft 1 intro-1 Offline Apps with HTML5 What if I told you that you don’t have to be online to use the Web? There’s a general (and understandable) belief by many developers, not to mention most users, that websites and web applications have a very serious limitation – they can only be used when the browser has a web connection. Indeed, this is routinely cited as one of the real advantages of so-called native apps over the Web. As counter-intuitive as it sounds, in almost every modern browser on any device (including IE10 and up), it’s no longer the case that users need to be connected to the Web to use our websites and applications, provided we developers do a little extra work to make our site or application persist when a browser is offline. This opens up a whole range of opportunities, leveling the field with native apps that can be installed on the user’s phone, tablet, laptop or desktop computer, or indeed any other device capable of running apps. But there are many more benefits to offline technologies than simply allowing websites and apps to work offline, as we’ll soon discover. Offline First Recently the team behind the “Hoodie” framework published “Offline first”1 a new way of thinking about developing for the Web. They observe that even in the developed world, mobile bandwidth and connectivity, increasingly the primary way in which people connect to the Web, are not always guaranteed to be there, or be reliable, and, they state: “We can’t keep building apps with the desktop mindset of permanent, fast connectivity, where a temporary disconnection or slow service is regarded as a problem and communicated as an error.” And when we think of offline and online, we typically only focus on the client, but servers go offline as well, both for routine maintenance, or in times of crisis, or under heavy stress.
    [Show full text]
  • Advanced HTML5 and CSS3 Specialist Exam 1D0-620
    Advanced HTML5 And CSS3 Specialist Exam 1D0-620 Domain 1: HTML5 Essentials 1.1 Consider HTML5 development skills you can apply to both traditional and non-traditional delivery platforms, including mobile apps. 1.2 Identify the Web development trifecta and explain its significance. 1.3 Explain the evolution of HTML and its relevance to modern design techniques. 1.4 Create and deploy HTML5 structure tags. 1.5 Perform HTML5 code validation, which includes explaining the practical value of code validation and listing the steps to validate HTML5 code. 1.6 Explain the importance of universal markup creation. 1.7 Apply the HTML5 <video> element appropriately. 1.8 Use the HTML5 <audio> element. 1.9 Define common elements of HTML5 application programming interfaces (APIs). Domain 2: Using Cascading Style Sheets (CSS) Technology 2.1 Explain the function and purpose of the Cascading Style Sheets (CSS) technology. 2.2 Explain the importance of using style guides when designing sites and documents. 2.3 Define common CSS terms and syntax. 2.4 Apply CSS styles to format pages. 2.5 Develop and apply page layouts with CSS. 2.6 Use CSS to position content and apply document flow. 2.7 Define common CSS positioning schemes. 2.8 Use the CSS Box Model. Domain 3: Introduction to CSS Version 3 (CSS3) 3.1 List the features added to CSS functionality in CSS version 3 (CSS3). 3.2 Apply common CSS3 properties and selectors. 3.3 Apply backgrounds and borders with CSS3. 3.4 Apply fonts and text effects with CSS3. Certification Partners, LLC - 1.800.228.1027 - 1.602.275.7700 www.CIWcertified.com - www.Certification-Partners.com Domain 4: Using Advanced CSS3 Techniques 4.1 Apply 2D and 3D transformations with CSS3.
    [Show full text]
  • Browser Security Principles: the Same-Origin Policy
    Secure Beginner’s Guide / Web Application Security, A Beginner’s Guide / Sullivan and Liu / 616-8 / Chapter 5 CHAPTER 5 Browser Security Principles: The Same-Origin Policy 149 05-ch05.indd 149 10/11/11 3:53:53 PM Secure Beginner’s Guide / Web Application Security, A Beginner’s Guide / Sullivan and Liu / 616-8 / Chapter 5 150 Web Application Security: A Beginner’s Guide We’ll Cover ●● Defining the same-origin policy ●● Exceptions to the same-origin policy any of the security principles we’ve talked about and will talk about in this book Mdeal with protecting your server resources. You want to be sure that unauthorized users can’t access the system; you want to be sure that attackers can’t break into your databases and steal your data; you want to be sure that no one can slow your system down so that it’s unavailable for everyone else. And it’s vital that you do defend against these kinds of attacks, but this chapter will focus on a completely different yet equally important area; specifically, we’ll be focusing on the principles of browser security. Web browsers have controls built into them in order to prevent malicious web sites from stealing users’ personal data. Browsers restrict the ways that web pages can communicate with web servers and with other windows in the browser. However, they only slightly restrict these communications—they couldn’t block them completely, or the web would be a pretty boring place. Usually, these subtle limitations are enough to thwart would-be attackers.
    [Show full text]
  • Jquery.Ajax() | Jquery API Documentation
    Plugins (https://plugins.jquery.com/) Contribute (https://contribute.jquery.org/) Events (https://js.foundation/events) Support (https://jquery.org/support/) JS Foundation (https://js.foundation/) Support the JS Foundation (https://js.foundation/about/donate) Download (http://jquery.com/download/) API Documentation (http://api.jquery.com/) Search Blog (http://blog.jquery.com/) Plugins (http://plugins.jquery.com/) Browser Support (http://jquery.com/browser-support/) Ajax jQuery.ajax() (http://api.jquery.com/category/ajax/) Global Ajax Event Handlers (http://api.jquery.com/category/ajax/global- Categories: Ajax (http://api.jquery.com/category/ajax/) > Low-Level Interface (http://api.jquery.com/category/ajax/low-level-interface/) ajax-event-handlers/) jQuery.ajax( url [, settings ] ) Returns: jqXHR (http://api.jquery.com/Types/#jqXHR) Helper Functions (http://api.jquery.com/category/ajax/helper- Description: Perform an asynchronous HTTP (Ajax) request. functions/) Low-Level Interface jQuery.ajax( url [, settings ] ) version added: 1.5 (/category/version/1.5/) (http://api.jquery.com/category/ajax/low- level-interface/) url Type: String (http://api.jquery.com/Types/#String) Shorthand Methods A string containing the URL to which the request is sent. (http://api.jquery.com/category/ajax/shorthand- methods/) settings Type: PlainObject (http://api.jquery.com/Types/#PlainObject) Attributes A set of key/value pairs that configure the Ajax request. All settings are optional. A default can be set for any option with $.ajaxSetup() (/jQuery.ajaxSetup/). See jQuery.ajax( settings ) below for a complete list of (http://api.jquery.com/category/attributes/) all settings. Callbacks Object (http://api.jquery.com/category/callbacks- jQuery.ajax( [settings ] ) version added: 1.0 (/category/version/1.0/) object/) settings Core Type: PlainObject (http://api.jquery.com/Types/#PlainObject) (http://api.jquery.com/category/core/) A set of key/value pairs that configure the Ajax request.
    [Show full text]
  • A Webrtc Based Platform for Synchronous Online Collaboration and Screen Casting
    A WEBRTC BASED PLATFORM FOR SYNCHRONOUS ONLINE COLLABORATION AND SCREEN CASTING by NIKOLAOS PINIKAS Master in Informatics and Multimedia, Department of Informatics Engineering, School of Applied Technology, Technological Educational Institute of Crete, 2016 A THESIS submitted in partial fulfillment of the requirements for the degree of MASTER OF SCIENCE IN INFORMATICS & MULTIMEDIA DEPARTMENT OF INFORMATICS ENGINEERING SCHOOL OF APPLIED TECHNOLOGY TECHNOLOGICAL EDUCATIONAL INSTITUTE OF CRETE 2016 Approved by: Assistant Professor Dr. Spyros Panagiotakis Copyright NIKOLAOS PINIKAS 2 0 16 This work is licensed under the Creative Commons Attribution 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by/4.0/. All included code is licensed under the MIT License. 2 “WebRTC is not a standard. It’s a movement.” -Tsahi Levent-Levi 3 Abstract WebRTC is a project that was released by Google in 2011 to allow browser- to-browser communication. It includes voice, video and data without the use of plugins. The mission of WebRTC according to Google is to enable rich, high quality, RTC applications to be developed for the browser, mobile platforms, and Internet of Things (IoT) devices, and allow them all to communicate via a common set of protocols. In this thesis we employ the capabilities of the WebRTC APIs to implement a platform for synchronous online collaboration, screen casting and simultaneous multimedia communication by utilizing the WebRTC data and media streams. Collaborative software is defined as “a software that supports intentional group processes”. Collaborative solutions include a wide range of tools. On the Web these tools can be part of what is known as a “Client-Portal” and can include discussions, white boards, media and file exchanging etc.
    [Show full text]
  • Using HTML5 Apis
    7Lesson 7: Using HTML5 APIs Objectives By the end of this lesson, you will be able to: 7.1: Define the Document Object Model (DOM). 7.2: Define application programming interface (API), and list the common HTML5 APIs. 7.3: Use the HTML5 Canvas API for advanced techniques. 7.4: Develop offline Web applications using the HTML5 AppCache API. 7.5: Use the HTML5 Geolocation API to obtain geographic information about a user. 7.6: Create drag-and-drop Web pages using the HTML5 Drag-and-Drop API. 7.7: Use the HTML5 File API to interact with files. 7.8: Use the HTML5 History API to manipulate a browser's history. 7.9: Retrieve and manipulate HTML5 data using XMLHttpRequest and jQuery. 7-2 Advanced HTML5 and CSS3 Specialist Pre-Assessment Questions 1. Which HTML5 API allows a Web program to run locally on a client system? a. Canvas b. AppCache c. Drag-and-Drop d. Geolocation 2. Which of the following is a function of the HTML5 File API? a. Create preview thumbnail images during image uploads b. Locate the position of the client system c. Move files using a drop zone d. Validate HTML5 code 3. What is the function of the HTML5 History API? © 2014 Certification Partners, LLC. — All Rights Reserved. Version 1.0 Lesson 7: Using HTML5 APIs 7-3 Introduction to HTML5 APIs As mentioned in an earlier lesson, experts in Web technology expect that the future of Web development will rely heavily on HTML5 APIs. HTML5 APIs consist of HTML5, CSS and JavaScript — the Web development trifecta.
    [Show full text]