Control ties the web server (view) to our database (model). In this implementation views are further defined using HTML files, Java classes will glue database stored procedure models containing SQL.
Example of Model View Control Thought Process
HTML5 files will use JavaScript to call APIs which determine the next step, or control. Models are entirely accessed in stored procedures within the database, via call statements, keeping CReate Update and Delete (CRUD) SQL separate from the decisions.
Security controls are also in the controller while delegating either an LDAP or DB model repository to store usernames and passwords.
These defined roles will allow changes to display formats; laptop vs mobile, or database; Derby vs Oracle, to evolve.
Don Cohoon 
Thanky Thanky for all this good infortmaoin!
LikeLike
Apperciaiton for this information is over 9000thank you!
LikeLike