[TYPO3-ect] MVC Project: CMEV scenario

Elmar Hinz elmar.DOT.hinz at team.MINUS.red.DOT.net
Mon Mar 6 08:41:06 CET 2006


Elmar Hinz schrieb:
> Because people seldom read long postings I will divide it into 3
> postings: introduction, error service, evaluator.
> 

Hello typoniks,

it just came into my mind that a 4th posting of an example scenario
would be of advantage in advance, a registration form.

A: The Form

The registration data consist of 3 values: email, username, password.
So we get one field for the email and the username each, 1 or 2 for
the password and optionally one for a captcha.

B: Different levels of evaluations

1.) format client tests: Javascript can do tests for empty fields,
email format and equality of the 2 form fields.

2.) format server tests: The same fields can be tested on the server.

3.) logical application tests: If the selected username or email is
already taken can't be found out by format tests. This can only be
done by application logic.

The captcha test can be done on level 2.) (session based) or level 3.)
(db based).

C: Diffrent Frontends:

There can be different frontend for this data. If the password data is
 proved by double input is irrelevant for the model. It is similar for
captcha.


D: Theses:

a.) For the user it is not interesting on which level the storing
fails. He simply want's a uniform response that tells him what input
went wrong. The system needs a service to collect errors from the
differnt levels and to provide the answers in a uniform way.

b.) The system needs to by flexible enough to provide diffferent
checks for different frontends.

c.) This flexible functinality should by reachable with as less
programming as possible. The greater part should follow automatically
out of the TCA.

/el






















More information about the TYPO3-team-extension-coordination mailing list