Communication Module
The main module
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Essential
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Marten de Vries
- Completed by
- Marten de Vries
Whiteboard
It would be nice if the communication module doesn't depend on one type of network. For example, we can have IRC next to XMPP next to a 'local' chat server which handles the web application requests. An implementation of this idea is Marten's test code.
-> IRC implemented, web chat too, possible to extend with other protocols but not necessary at the moment.
Commands (links, questions, answers, etc., next slide) are sent over the chat network, to keep it accessible for non-JFL users.
-> check.
Possible commands/ways of communication:
- CLASS <- teach, done.
- CHAT <- chat, done
- QUESTION <-ask, done
- ANSWER <-answer, done
- LINK <-sendLink (automatically handled by ChatHandler), done
- DROP QUESTION <- done
- SLOW DOWN <- NOT STARTED <- No need, chat will do. Or a question 'can you slow down a bit, please?'
- TAKE A BREAK (mentor only) <- NOT STARTED <- No need, possible to say that in class.
libtelepathy? <- No!
