#23: Desktop or CLI client
--------------------------+--------------------
Reporter: pingou | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: Future
Component: API | Version:
Resolution: | Keywords:
--------------------------+--------------------
Comment (by bex):
Thinking about this a bit more, should we consider refactoring the
application into a separate front-end and back-end?
back-end: Manage the DB of events and editing; Send emails; create a new
complete static .ics file after every edit.
front-end: read and display static .ics files; serve .ics urls for other
clients; aggregation, and sub-calendaring, etc. as referenced in tickets
like #53 and #161. This would also solve #156 as .ics files could always
be complete with negligible load.
--
Ticket URL: <
https://fedorahosted.org/fedocal/ticket/23#comment:2>
fedocal <
https://fedorahosted.org/fedocal>
A web-based calendar application for Fedora