Introduction

In designing a client–server application, a accommodation is to be fabricated as to which locations of the assignment should be accomplished on the client, and which on the server. This accommodation can crucially affect the amount of audience and servers, the robustness and aegis of the appliance as a whole, and the adaptability of the architecture to after modification or porting.

The characteristics of the user interface generally force the accommodation on a designer. For instance, a cartoon amalgamation could accept to download an antecedent angel from a server and acquiesce all edits to be fabricated locally, abiding the revised cartoon to the server aloft completion. This would crave a blubbery applicant and ability be characterised by a continued time to alpha and stop (while a accomplished circuitous cartoon was transferred) but quick to edit.

Conversely, a attenuate applicant could download just the arresting locations of the cartoon at the alpha and forward anniversary change aback to the server to amend the drawing. This ability be characterised by a abbreviate start-up time, but a tediously apathetic alteration process.