Chrome Release Bot (LUCI) 4762b62e7d Publish DEPS for 106.0.5249.13 1 anno fa
..
content 4762b62e7d Publish DEPS for 106.0.5249.13 1 anno fa
core 4762b62e7d Publish DEPS for 106.0.5249.13 1 anno fa
mojom 4762b62e7d Publish DEPS for 106.0.5249.13 1 anno fa
COMMON_METADATA 4762b62e7d Publish DEPS for 106.0.5249.13 1 anno fa
DEPS 4762b62e7d Publish DEPS for 106.0.5249.13 1 anno fa
DIR_METADATA 4762b62e7d Publish DEPS for 106.0.5249.13 1 anno fa
OWNERS 4762b62e7d Publish DEPS for 106.0.5249.13 1 anno fa
README 4762b62e7d Publish DEPS for 106.0.5249.13 1 anno fa

README

This directory contains shared code used by multiple platforms' native
implementations of PaymentRequest. In general, business logic (i.e., logic which
manipulates data and is not specific to any particular platform's display of the
data) should live here as much as possible.


Internally, the directory uses the Layered Components model:

http://www.chromium.org/developers/design-documents/layered-components-design


In practical terms, our division between content/ and core/ is usually just a
question of whether the contents have a dependency on Mojo:

* ./core/ -- preferred whenever possible

* ./content/ -- code with a Mojo dependency

* ./content/android/ -- Android bindings for code in either core/ or content/


Intended consumers of this code are organized as follows:

* chrome/android/.../chrome/browser/payments/ -- Android UI Implementation

* chrome/browser/ui/views/payments/ -- Desktop UI implementation

* content/browser/android/payments -- Android bindings for PaymentApps

* content/browser/payments/ -- PaymentApps implementation

* ios/chrome/browser/payments/ -- iOS UI implementation

* ios/web/payments/ and ios/web/public/payments/ -- iOS communication layer,
replacing Mojo