Scope: managed applications, mobile applications, and ordinary applications.
1.1. You need to minimize the amount of the code executed on the client application side. Specifically, do not execute complex algorithms, which require a lot of computer resources, on the client. In such cases, algorithm execution on the client can be more time-consuming than control transfer from the client to the server, algorithm execution on the server, and return of the result back to the client.
You need to place such algorithms in a server code and minimize the number of calls to them made from the client.
See also: Minimizing the number of server calls
This requirement is dictated by the following:
- Usually, the client computer is less powerful than the server one.
- There is a need for acceptable user experience in web client. A client code is executed by the 1C:Enterprise language interpreter that works significantly slower in web client than on the thin or thick client.
1.2. It is recommended that you place on the client algorithms whose execution is less time-consuming than a call of a server function. For example, when a user changes data, controls availability in a form is recalculated on the client as a context server call in a complex form might hinder user operations.
2.1. An exception to this rule are cases when a functional subsystem is used to work with software installed on the client computer. For example, operations with shop fixtures and fittings, integration with client bank, generation of print forms for office applications, and so on.
#If WebClient Then
Warning(Nstr("en = "Address classifier import is unavailable in web client."));