Changes

Jump to navigation Jump to search
Line 118: Line 118:  
* '''Details''': Although XMPP has supported multiple simultaneously connected clients from the start, the user experience is in practice seldom what a user would expect. This has not been a big problem up until recently, since most people tend to connect with only one client at the same time. These days, however, people are constantly going back abd forth between their always-on mobile IM client and their desktop. Enabling a good user experience for this requires new protocols and techniques for transferring conversations between devices, ... This project is about implementing these protocols to streamline the use case of multiple resources
 
* '''Details''': Although XMPP has supported multiple simultaneously connected clients from the start, the user experience is in practice seldom what a user would expect. This has not been a big problem up until recently, since most people tend to connect with only one client at the same time. These days, however, people are constantly going back abd forth between their always-on mobile IM client and their desktop. Enabling a good user experience for this requires new protocols and techniques for transferring conversations between devices, ... This project is about implementing these protocols to streamline the use case of multiple resources
   −
=== Constrained Swifts ===
+
=== Constrained Swift ===
 
* '''Summary''': Implement support for XMPP protocols that are targeted towards (resource-)constrained environments
 
* '''Summary''': Implement support for XMPP protocols that are targeted towards (resource-)constrained environments
 
* '''Difficulty''': Medium
 
* '''Difficulty''': Medium
20

edits

Navigation menu