Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a227175559cc845c

Jump to content

Layer (object-oriented design)

From Wikipedia, the free encyclopedia

In software object-oriented design, a layer is a group of classes that have the same set of link-time module dependencies to other modules.[1] In other words, a layer is a group of reusable components that are reusable in similar circumstances. In programming languages, the layer distinction is often expressed as "import" dependencies between software modules.

Layers are often arranged in a tree-form hierarchy, with dependency relationships as links between the layers. Dependency relationships between layers are often either inheritance, composition or aggregation relationships, but other kinds of dependencies can also be used.

Layers is an architectural pattern described in many books, for example Pattern-Oriented Software Architecture[2]

See also

[edit]

References

[edit]
  1. Lakos, John (1997). Large-scale C++ software design'. Addison-Wesley.
  2. Pattern-Oriented Software Architecture - A System of Patterns Archived 2008-06-16 at the Wayback Machine