Roster is currently based on presences that have voip. To turn this into a proper chat/voip app the following is required:
1) Hook up roster in our app, to actual roster changes in RosterHandler, reusing events that are already created in clientsignalingthread.cc for ROSTER_ADD/REMOVE/RESET.
2) Will have to probably change the RosterItem struct to include bool voip.
2) Remove OnStatusUpdate method(fake roster implementation) and the signalstatusupdate method.
First partial refactor commit that enabled roster, and wrapped the old incorrect functionality.
Roster is currently based on presences that have voip. To turn this into a proper chat/voip app the following is required:
1) Hook up roster in our app, to actual roster changes in RosterHandler, reusing events that are already created in clientsignalingthread.cc for ROSTER_ADD/REMOVE/RESET. 2) Will have to probably change the RosterItem struct to include bool voip. 2) Remove OnStatusUpdate method(fake roster implementation) and the signalstatusupdate method.
First partial refactor commit that enabled roster, and wrapped the old incorrect functionality.
https://github.com/lukeweber/webrtc-jingle-client/commit/23c3c66a2e1d55cfb0c81e516003f41f989993b1