http://anupfrancis.com/?p=30 wrote:Sun(TM) Certified Ajax Developer (CX-310-700) exam.
Section 1 - JavaScript Fundamentals

* Objective 1.1
Create JavaScript applications that use standard (ECMAScript 262 v3) language elements for object-based programming; including, creating objects, using the "new" operator, adding and accessing members, creating and executing methods. Describe the effects of modifying the prototype object of constructor functions.
* Objective 1.2
Create JavaScript applications that use standard language elements for functional programming; including, creating named and anonymous functions, using closures, understanding parameter passing semantics, understanding the variable scoping rules, and using the "apply" and "call" functions.
* Objective 1.3
Create JavaScript applications that use pseudo-classical and prototypal inheritance patterns; including, creating constructor functions, creating instance methods using the constructor prototype, using closures, and using delegation and composition as alternatives to class-based inheritance.
* Objective 1.4
Describe how to transform JavaScript objects and data structures to and from string format via the JavaScript Object Notation (JSON, see http://www.json.org/). Create JavaScript applications that apply this knowledge and uses the Dojo-based JSON facilities.

Section 2 - DOM Fundamentals

* Objective 2.1
Create JavaScript applications that use standard APIs (from the W3C levels 1 and 2 DOM specifications) to access document object model (DOM) elements of the HTML page.
* Objective 2.2
Create JavaScript applications that use standard APIs (from the W3C levels 1 and 2 DOM specifications) to traverse DOM nodes of the HTML page. Describe the issues with the standard DOM traversal APIs and cross-browser support.
* Objective 2.3
Create JavaScript applications that use standard APIs (from the W3C level 2 DOM specification) to manipulate the DOM structure of the HTML page.
* Objective 2.4
Create JavaScript applications that use standard APIs (from the W3C level 2 DOM specification) to register and handle events on the DOM structure of the HTML page. Describe the issues with the standard DOM events APIs and cross-browser support.

Section 3 - Ajax Fundamentals

* Objective 3.1
Create JavaScript applications that use ad-hoc browser support for creating an asynchronous HTTP request to a web server; including, the de-facto standard APIs on the XMLHttpRequest (XHR) class.
* Objective 3.2
Describe the life cycle of an Ajax request using the de-facto standard APIs on the XMLHttpRequest class.
* Objective 3.3
Create JavaScript code that handles Ajax requests using the de-facto standard APIs on the XMLHttpRequest class; including, processing the response as text, XML, JSON, and raw JavaScript code.

Section 4 - The Dojo Framework

* Objective 4.1
Describe why it is important to use a high-level JavaScript framework, such as Dojo, including issues around cross-browser support, incomplete and awkward standard DOM APIs, ease of development, and so on.
* Objective 4.2
Create JavaScript code to select DOM elements using Dojo?s selector functions, byId and query, including querying by common CSS selector syntax.
* Objective 4.3
Create Rich Internet Applications (RIAs) using Dojo's Base and Core APIs, including support for DOM traversal and manipulation, browser detection, and additional functional programming facilities built into the Dojo NodeList APIs.
* Objective 4.4
Create RIAs that take advantage of the message-based and event-driven programming styles that are facilitated by Dojo's event and message communication APIs, including using the dojo.connect and dojo.subscribe functions.
* Objective 4.5
Create RIAs that make asynchronous Ajax requests to the server using Dojo's XHR APIs, including applying Deferreds and chaining Ajax event handlers.
* Objective 4.6
Create RIAs that make use of Dojo's object-oriented programming APIs, including the dojo.declare, dojo.extend, and dojo.mixin functions; including how to mimic single, multiple, and mixin class inheritance; and including the object life cycle methods.
* Objective 4.7
Create RIAs that make use of Dojo's data programming APIs, including the Identity, Read, Notification, and Write interfaces; including a few simple implementations of these interfaces (ItemFileReadStore and ItemFileWriteStore); and including the semantics of asynchronous behavior, such as fetch.

Section 5 - The Dojo Widgets

* Objective 5.1
Create RIAs that make use of Dojo's widget APIs (called "dijits"), including creating dijits defined in HTML markup or in JavaScript, including use of the dijit life cycle methods, and including knowing how to inject parameters into templated dijits.
* Objective 5.2
Create RIAs that make use of Dojo's basic application dijits, including major container dijits and these specific dijits: Tree, Dialog, ProgressBar, and Tooltip.
* Objective 5.3
Create RIAs that make use of Dojo's form dijits, including all standard HTML widget replacements and these specific dijits: ValidationTextBox. ComboBox, and FilteringSelect.
* Objective 5.4
Create RIAs that make use of Dojo's dijit building APIs to create new UI widgets, including creating a templated dijit, and including using existing Dojo classes and mixins to create new dijits.

Section 6 - Programming Practices and Patterns

* Objective 6.1
Create a secure RIA by applying security considerations of using Ajax, JSON, and other RIA technologies. Describe the security risks of an Ajax-enabled web application. Describe or apply solutions to these security risks in you client-side code.
* Objective 6.2
Create a well-designed RIA using common client-side design patterns, including describing and applying unobtrusive JavaScript techniques and including common web UI design patterns.
* Objective 6.3
Create RIAs that communicate with web servers using Java-based, server-side technologies such as Servlets, JavaServer Pages, the JSON Java APIs to handle both page-level and Ajax-level HTTP requests. Describe techniques for augmenting the HTTP response using compression, minimization, and cache-prevention.
* Objective 6.4
Describe common gotchas in client-side programming, such as issues with the DOCTYPE, resource caching, and CSS quirks. Describe how to debug RIA client-side code using browser environments such as Firebug and IE's Developer Toolbar. Describe techniques for unit testing client-side coding using Dojo's DOH facility.

Leonardo3001 wrote:Totalmente estranho o uso de Dojo, que é talvez menos popular que JQuery, Prototype e Mootools.

faelcavalcanti wrote:bem mais enriquecedor estudar com sang em ajax programming durante 3 ou 4 meses

Leonardo3001 wrote:Totalmente estranho o uso de Dojo, que é talvez menos popular que JQuery, Prototype e Mootools.