As already cited at the GSoC's proposal, the Media Server would use pubsub capabilities to give/deny access a channel's media.
Although the concept is quite simple, and the necessary packets to trade such information between a client and a pubsub server, the biggest challenge was adapt the Smack API to the particularities from the buddycloud's XEP. The work was a lot easier because in the last year GSoC, another buddycloud's student (Abmar Barros) had to implement similar functionality into his project, also using Smack.
So, to verify if an user like "firstname.lastname@example.org" can POST a media into "email@example.com" all that the Media Server does is retrieve the channel's affiliations, and check if "firstname.lastname@example.org" has post capabilities:
<iq from="email@example.com/Client" id="Eq5j2-2" to="channels.buddycloud.org" type="get"> <pubsub xmlns="http://jabber.org/protocol/pubsub#owner"> <affiliations node="/firstname.lastname@example.org/posts"> </affiliations></pubsub> </iq>
<iq from="channels.buddycloud.org" id="Eq5j2-2" to="email@example.com/Client" type="result"> <pubsub xmlns="http://jabber.org/protocol/pubsub#owner"> <affiliations xmlns="http://jabber.org/protocol/pubsub#owner"> <...> <affiliation jid="firstname.lastname@example.org" affiliation="publisher"/> </affiliations> <set xmlns="http://jabber.org/protocol/rsm"> <first index="0"> email@example.com </first> <last> firstname.lastname@example.org </last> <count> 5 </count> </set> </pubsub> </iq>
What are the next steps?
- Fist I'd like to deploy a toy client to demonstrate some of the Media Server functionality; - After that, the next step is the implementation of the XEP-0070 and documentation.