itotallyrock
commented
7 years ago This is similar to #46 and attempts to accomplish the same goal but offers more logic to it. It would be nice to have events stored in a similar fashion to badges, users, and bugreports. Since all of those features interact nicely and having one strange element to it really threw the whole thing off. It will be nice to have events along side the other collections in the database.
Have a server that listens for calendar events (Google calendar watch api). This server will then update the information in the database. This way we can always have a local version of the calendar which is interactive. This allows for custom attributes to events like: attendees, local time, event type, etc. Which are all features that are currently filled in on the local end or not even possible. This also means less calculations too, since currently when checking into an even if an event is labeled by address we have to request each checkin to get its latitude and longitude from address. Whenever the webserver needs access to the information it will still be stored in the same database and easily accessed and changed. This will remove all need to non-persistent runtimes.