Tersus: Re: New Documentation - Action/Service/Callable Service templates

Re: New Documentation - Action/Service/Callable Service templatesDate: Nov 23, 2007Minimizing client-server requests is very important to improve performance.Consider for example the following model, deleting all records from a database table: Inefficient

We have one client-server request for 'Find', and then multiple requests for 'Delete'. If the table contains 10 records, we'll have a total of 11 requests. If it contains 1000 records, we'll have 1001 requests. We also pass a lot of data from the server to the client, and then back from the client to the server.
This is extremely inefficient A much better model would pack both 'Find' and 'Delete' in a single service, like this: One

Now we have only a single client-server request, regardless of the amount of work that has to be done, and no records are passed between the client and the server. This is optimal.A few improvements I think we should introduce:

Indicate clearly services (like 'Find'), client-side actions (like 'Close Window'), and "flexible" actions that can take place on either the client or the server.

Add 'Service Cardinality', counting how many services there are in a non-service model. In the above example, the first 'Delete All' button has service cardinality 'Indefinite', because it might invoke an indefinitely big number of service requests, which is bad. The second 'Delete All' button has service cardinality 1, which is good.

Add a warning if a client-side model has service cardinality higher than 1. This is usually an indication of a problem, calling for the packing of several sub-processes within a single service.