reservat / core Goto Github PK

Config is there to do the work.

L22 AvailabilityMatrix.js - Use the config on restaurant.

So the current state of this:

We have time slots
We have available tables

My plan is to end up with something akin to this. (psuedocode)

[{
  8:45 : {tblNum : bookingId || false} /* for each table */
}]

This should make an easily queryable hashmap.
To generate that hashmap I'm envisaging a promise that can fail quickly if it knows all tables that would be available for this booking request are already filled.
I'm concerned about performance here as I think this could take a while...

A user can have many sessions.
There are 3 types of session.

application
Only granted when the user is using the reservat application, raised perms.
api
Long lived tokens for users to access the API. controlled permissions.
customer
Basic perms to be able to make bookings and communicate with the set restaurant through websockets.

The only thing stored user side will be a sessionID in cookies or local storage.
Cookies will have a set expiration date, but the session will also have an expiration stored inside Redis.

As per the user implementation.

Reservat core class should pass down singleton wrapper classes for ElasticSearch/MySQL/Redis.

Tables should have an allocation priority - so the best tables are available first and lesser used tables can be allocated as a last resort.