Today Gavin, Daniel, and I met to discuss and complete the architecture assignement. Gavin address a huge concern that he was having about authentication. Apparently OAuth authentication with google requires that a user login to Google through a browser after which an authentication token will be created and passed back to the application. The problem is that as far as we know, the printer doesn't have a browser and thus OAuth may not be possible. If it's not possible then we will either have to access public browsers or figure out a different means of authentication.
We started out the meeting discussing the user stories and we built up a high level overview from this. From there we fleshed out a fairly comprehensive class diagram over the course of the next 2 hours. Some major design points that we discussed was adding interfaces for the Google Calendar Service as well as the Google Authentication Manager which are CalendarService and AuthenticationManager respectively. The reason we did this was to allow for other calendar services to be plugged into the AppController without requiring modification to it's logic.
We also decided on implementing an MVC architecture so that we could keep the business logic separate from the view.
As of now we are also unsure of another major design decision which has to do with multi-threading. We are not positive what facilities are available to us for multithreading but we feel it will be necessary as we are hoping to show a short dialog during printing and sending an email and having a callback being invoked when they complete, however we don't want to block as the user may still want to look through the different meetings for that day while the email is sending or while printing.
Authentication Problem
Spawning a new thread for printing.
No comments:
Post a Comment