Unified Modeling Language UML logo The Unified Modeling Language (UML) is a general-purpose modeling language in the field of software engineering, which is designed to provide a standard way to visualize the design of a system. It was created and developed by Grady Booch, Ivar Jacobson and James Rumbaugh at Rational Software in the 1990s. In 1997 it was adopted by the Object Management Group (OMG), and has been managed by this organization ever since. In 2000 the Unified Modeling Language was accepted by the International Organization for Standardization (ISO) as an approved standard. Since then it has been revised to cover the latest revision of UML. Overview A collage of UML diagrams. The Unified Modeling Language (UML) offers a way to visualize a system's architectural blueprints in a diagram (see image), including elements such as: History History of object-oriented methods and notation. Before UML 1.x UML 1.x UML 2.x There are four parts to the UML 2.x specification: 
HTTP/2 technology demo What is CakePHP? Why Use it? Improve this Doc CakePHP is a free, open-source, rapid developmentframework for PHP. It’s a foundational structure for programmers to create web applications. Our primary goal is to enable you to work in a structured and rapid manner–without loss of flexibility. CakePHP takes the monotony out of web development. It provides you with all the tools you need to get started coding and what you need to get done: the logic specific to your application. CakePHP has an active developer team and community, bringing great value to the project. Here’s a quick list of features you’ll enjoy when using CakePHP:
Model–view–controller Model–view–controller (MVC) is a software pattern for implementing user interfaces. It divides a given software application into three interconnected parts, so as to separate internal representations of information from the ways that information is presented to or accepted from the user. The central component, the model, consists of application data, business rules, logic and functions. A view can be any output representation of information, such as a chart or a diagram. Multiple views of the same information are possible, such as a bar chart for management and a tabular view for accountants. Component interactions A typical collaboration of the MVC components In addition to dividing the application into three kinds of components, the Model–view–controller (MVC) design defines the interactions between them. Use in web applications History See also References External links
Getting Started Welcome to CakePHP. You’re probably checking out this tutorial because you want to learn more about how CakePHP works. It’s our aim to increase productivity and make coding more enjoyable: we hope you’ll see this as you dive into the code. This tutorial will walk you through the creation of a simple blog application. Here’s what you’ll need: A running web server. Let’s get started! Getting CakePHP First, let’s get a copy of fresh CakePHP code. To get a fresh download, visit the CakePHP project on GitHub: and download the latest release of 2.0 You can also clone the repository using git. git clone Regardless of how you downloaded it, place the code inside of your DocumentRoot. /path_to_document_root /app /lib /plugins /vendors .htaccess index.php README Now might be a good time to learn a bit about how CakePHP’s directory structure works: check out the CakePHP Folder Structure section. Tmp directory permissions Note <! <!
Zend Framework & MVC Introduction - Zend Framework Quick Start Zend Framework Zend Framework is an open source, object oriented web application framework for PHP 5. Zend Framework is often called a 'component library', because it has many loosely coupled components that you can use more or less independently. But Zend Framework also provides an advanced Model-View-Controller (MVC) implementation that can be used to establish a basic structure for your Zend Framework applications. This QuickStart will introduce you to some of Zend Framework's most commonly used components, including Zend_Controller, Zend_Layout, Zend_Config, Zend_Db, Zend_Db_Table, Zend_Registry, along with a few view helpers. Using these components, we will build a simple database-driven guest book application within minutes. Model-View-Controller So what exactly is this MVC pattern everyone keeps talking about, and why should you care?
The HTTP OPTIONS method and potential for self-describing RESTful APIs The OPTIONS method is a somewhat obscure part of the HTTP standard that could be used today with a strong impact on the interconnectedness of the interwebs while requiring minimal effort. It's role is well defined in RFC2616, yet no web services that I can find are taking advantage of it. To quote the spec: This method allows the client to determine the options and/or requirements associated with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval. Minimally, the response should be a 200 OK and have an Allow header with a list of HTTP methods that may be used on this resource. 200 OK Allow: HEAD,GET,PUT,DELETE,OPTIONS I've tested quite a few sites and APIs and so far, the only resources I've found that respond properly are default Apache pages. ... GitHub responds with a 500, Reddit with 501 Not Implemented, Google maps with 405 Method Not Allowed. GitHub (to pick on someone specific. APIs should be taking advantage of this.
ECMAScript 5 Strict Mode, JSON, and More Previously I analyzed ECMAScript 5’s Object and Property system. This is a huge new aspect of the language and deserved its special consideration. There are a number of other new features and APIs that need attention, as well. Strict Mode Strict Mode is a new feature in ECMAScript 5 that allows you to place a program, or a function, in a “strict” operating context. Since ECMAScript 5 is backwards-compatible with ECMAScript 3, all of the “features” that were in ECMAScript 3 that were “deprecated” are just disabled (or throw errors) in strict mode, instead. Strict mode helps out in a couple ways: It catches some common coding bloopers, throwing exceptions.It prevents, or throws errors, when relatively “unsafe” actions are taken (such as gaining access to the global object).It disables features that are confusing or poorly thought out. Most of the information about strict mode can be found in the ES5 specification [PDF] on page #235. How do you enable strict mode? Simple. // Non-strict code...
Hypertext Application Language Hypertext Application Language (HAL) is an Internet Draft (a "work in progress") standard convention for defining hypermedia such as links to external resources within JSON or XML code. The standard was initially proposed on June 2012 specifically for use with JSON and has since become available in two variations, each specific to JSON or XML. The two associated MIME types are media type: application/hal+xml and media type: application/hal+json. HAL was created to be simple to use and easily applicable across different domains by avoiding the need to impose any requirements on how the project be structured. APIs that adopt HAL are generally more appealing to developers[neutrality is disputed] because it simplifies the use of open source libraries and makes it possible to interact with the API using JSON or XML. Convention HAL is structured in such a way as to represent elements based on two concepts: Resources and Links. See also References External links
Storing Objects in HTML5 localStorage