Wed, 26 Aug 2015 19:38:35 -0700 Lance Stout <lancest...@gmail.com> wrote:
> To that end, I submitted an update to XEP-0264 today to get it out of > the Deferred state, allow it to use other URI types, and expand its > scope to more than just file transfer thumbnails (for example, > attaching a thumbnail preview to RTP video streams). A rendered > version of the PR is available at > http://legastero.github.io/customxeps/extensions/xep-0264.html. Looks nice, thank you. I wish Council would accept the changes despite Marcus (the author) is inactive for a very long time. > Use within MUC is an issue with any Jingle session type and > transport. XEP-0358 (Publishing Available Jingle Sessions, aka > JinglePub) is intended as a solution for that problem. JinglePub > works via a similar mechanism as what is proposed in > https://github.com/processone/ejabberd-saas-docs/blob/master/xmpp-specs/http-filetransfer/http-filetransfer.md, > but is usable with any type of Jingle session. An example for a MUC case would be appreciated. From the XEP I understood nothing. Also, how will this interact with legacy clients (old unsupported XMPP clients, mostly 95% of all clients)? In the case of HTTP Upload any client will be able at least to see the link and download the file. > Starting a Jingle session with an offline user is naturally an issue > with any Jingle session type. Using XEP-0353 (Jingle Message > Initiation) or XEP-0358 in combination with XEP-0357 (Push > Notifications) is intended as a foundation for a general solution. I don't think XEP-0353 (Jingle Message Initiation) will help because it requires the initiator to be available in order to receive message-accept which is not always the case. I'm not sure if XEP-0357 (Push Notifications) may help here, I thought it was designed for a different purpose.
