Student projects/Chat revamp: Difference between revisions
From MoodleDocs
| Line 11: | Line 11: | ||
==Core functions== | ==Core functions== | ||
• Front end work, integrate Moodle with Jwchat, which would be essential and should do in PHP. | • Front end work, integrate Moodle with Jwchat, which would be essential and should do in PHP. | ||
• Integrating ejabberd to do the back end work. This will require authentication between Moodle and ejabberd, single sign-on (SSO), automatic roster creation and group chats. This part will be implemented using Erlang. | • Integrating ejabberd to do the back end work. This will require authentication between Moodle and ejabberd, single sign-on (SSO), automatic roster creation and group chats. This part will be implemented using Erlang. | ||
Revision as of 06:03, 19 June 2007
Programmer:
Suggested headings, feel free to add/remove ..
Summary
"Chat Revamp" is an attempt to increase the capabilities of the Moodle chat. It would be based on integrating the ejabberd back end and doing necessary changes to the front end as well. Integrating ejabberd will improve the performance of the Moodle chat while improving the features as it is a high performance instant messaging server.
Database structures
Core functions
• Front end work, integrate Moodle with Jwchat, which would be essential and should do in PHP.
• Integrating ejabberd to do the back end work. This will require authentication between Moodle and ejabberd, single sign-on (SSO), automatic roster creation and group chats. This part will be implemented using Erlang.
Interface mockups
Tasks and Timeline
See also
Back to: Student projects
