Application and database API design

[whymarrh]

Discuss.

[whymarrh]

I feel that the database and API portions should reside in a new module separate from AbaLookup. (I'm fairly confident I fixed the issue that lead me to dismiss this option previously.) This module would include the database wrapper (#94), a simple object mapper, the matching algorithm (#29), and a public API. We could called it something generic like Matcher.

As for the methods we'll need exposed for the API, I can think of a few:

• $api->createUser(array $options);
• $api->getUserById(int $id);
• $api->getUserByEmailAddress(string $email);
• $api->updateUser(User $user);
• $api->getUserTypes();
• $api->getScheduleForUser(User user);
• $api->updateSchedule(Schedule $s);

Question: should/could we move the form validation into the API and have the forms send their data there?

[MitMaro]

Results of the meeting on Oct 27, 2013

[whymarrh]

@MitMaro Is this up next for discussion?

To be completely honest, I don't remember much (read: any) of the details — I know we had a design in mind that separated the database/object mapper from the controllers? That picture has no answers.