Hi Daniel, Perhaps it'd be sensible to always add a reference to the desired retention policy - also for temporary slots. Perhaps the server should answer with the applied policy too?
Regards, Guus On 8 September 2017 at 10:58, Daniel Gultsch <[email protected]> wrote: > 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: [email protected] > _______________________________________________ >
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
