Showing posts from June, 2017

Week 4

Hello all,
This week was a productive week ! I completed all the elements required for MIX implementation along with their parsers, serializers, and unit tests. The elements completed this week along with their XML examples (taken from XEP) are as follows: Create Element: A client creates a channel by sending a simple request to the MIX service.<createchannel='coven'xmlns='urn:xmpp:mix:1'/>Destroy Element: A client destroys a channel using the destroy payload.<destroychannel='coven'xmlns='urn:xmpp:mix:1'/> Set Nick Element: The client sends a command to the channel to set / update the nick.<setnickxmlns='urn:xmpp:mix:1'><nick>thirdwitch</nick></setnick> Register Nick Element: The client sends a command to the channel to register the nick.<registerxmlns='urn:xmpp:mix:1'><nick>thirdwitch</nick></register> Update Subscription Element: The client can send a update subscription request …

Till Week 3 - Elements !

Hello all,
I am Tarun, a senior year student at IIIT Hyderabad, India. This year I was selected as a GSoC student by XMPP Standards Foundation to work on Mediated Information Exchange (MIX), which is intended as a replacement for Multi-User Chat (MUC). I'm being mentored by Tobias and Edwin. Let me begin by explaining why do we need MIX as a replacement for MUC ? In the years after MUC was designed, both Publish-Subscribe and Message Archive Managementhave been developed and it is desirable to reuse these building blocks (e.g., MAM can be used for message history) rather than using the less robust methods defined in Multi-User Chat .It is difficult to use MUC for building multimedia applications without undesirable adaptations.A number of use cases has emerged in group communication, which are explained here. I have started by implementing elements (payloads), which will be coming in / send out in the form of XML. Therefore, we need parsers and serializers for each payload to be a…