Scalability of remote validators

[bruno]

I have some concerns about the scalability of remote validators when there are more than a couple of them in one form (e.g. when part of collection).

When submitting a form, the form should first be validated, which includes calling the remote validators. This happens through non-async ajax calls. Lots of validators == lots of ajax calls to wait for.

Maybe this can be optimized in some way.

[mpo]

Proposed strategy:

Let's foresee a mechanism (flag in fconf + validator) on the AbstractContainer? widget that allows for validation (might not be remote even) to happen on that level in one go, while preventing the current delegation down to the children.

This can live in combination with the current child-level validation which will then only be triggered by the value-change of those children themselves.

(ToDo? however: Think what will then trigger the container-validation? Only at form-submit initiated or any direct isValid call? Possibly we get to start-validation-methods one to delegate down, one not to, both called during form-submit. Or some method or form state to control the work)

In this case it is up to the developer to anticipate possible scalability issues and foresee proper validators at proper levels.