Hi everyone, Based on the previous messages I'd like to do a proposal regarding the evolution of HTTP Upload.
The idea behind HTTP-Upload was to have this tiny-simple XEP that can handle upload of files through HTTP and return an URL that can be inserted everywhere in XMPP. It seems that people, like Daniel, are reaching the limits of those features and want to extend the XEP. What I'd like to propose, is to re-use Pubsub/PEP to handle and manage those files. Basically once a file is uploaded using HTTP-Upload, the server creates a new item on a designated PEP node (urn:xmpp:files:0 for example) and notify the publisher using a simple headline. This PEP node will list all the previously uploaded files, the items could contain all the metadata (using something like XEP-0385: Stateless Inline Media Sharing (SIMS) for example). This way, at any moment, the user can see what files are stored on the server and can easily manage/delete them. A hard-limit can also be put on the number of those items to only keep the latest 100 files uploaded (for example). All those mechanism are relying on existing XEPs and will require only a small adaptation on the servers and clients to handle that. I'm open to any proposal but I'd strongly prefer to re-use and push existing standards and defined XML namespaces than creating something from scratch for our needs. Regards, Timothée Jaussoin Le vendredi 08 septembre 2017 à 10:58 +0200, Daniel Gultsch a écrit : > Hi all, > > when I first came up with HTTP Upload it was intended to also provide > storage space for avatars and other permanent and public information. > The introduction even mentions this. > > However most servers currently have rather low retention periods of 10 > days or 30 days (which is fair). Uploading an avatar for example under > those conditions however isn't very feasible. > > That's why I propose to add the ability to optionally request slots > that are permanent. > Those permanent slots would have multiple types (avatar,...) and would > always overwrite each other. > > Syntax would probably look something like this. > > <request size="1234" filename="me.png"><permanent type="avatar"/></request> > > But I have a few questions: > > Do you think these types should be registered? > Should we use types at all? Or rather have some other limitation on > permanent slots? (Like user can only have 10? And old ones will always > be overwritten) > > cheers > Daniel > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > _______________________________________________ _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
