client layer

The client-layer methods are the only methods that are responsible for starting, committing, and rolling back the transaction.

Like the API Layer strategy, the High Concurrency strategy frees the client layer from any transaction responsibility.

Such variations might be caused by a gap in the systems model or by a unilateral change in the client layer.

The objective of pre-provisioned adaptation management community is to provide link capacity to client-layer(s) from a server layer.

Only methods in the client layer and the API layer of the application architecture should contain transaction logic.

JavaFX 2 represents a major update to the client-side Java stack, offering an alternative to the entire client layer of the JavaSE platform.

However, this also means that you can have only one call from the client layer for any given logical unit of work (LUW).

In essence, the client layer owns the processing flow and "steps" needed to complete a particular request.

The transaction context from the client layer will propagate to the API layer methods and all methods invoked under the API layer.

The latter contains three parts: data layer, service layer and client layer.

Notice in this strategy that both the client layer and the API layer contain transaction logic.

The prototype has three layers: the client layer, the agent layer and the server layer.

The client layer controls the transaction scope.

Typically you need to use programmatic transactions in the client layer.

If the application's API layer is too fine-grained, you have to invoke both methods from the client layer.

In this scenario, the transactional unit of work must reside in the client layer to ensure an atomic unit of work.

The first one is client layer.

Client Layer - used by application to communicate with SQL Azure