On Sat, Sep 2, 2017 at 10:37 AM, Adam Johnson <[email protected]> wrote: > ArchiveField sounds a bit too specific for Django core, the most common case > for uploading multiple files would probably be to access them individually, > which it would prevent.
Yeah, was on the fence on that one myself. The use cases are very domain specific, the obvious one being a backup application, but also design specs or legal documents that site staff downloads and never actually views on site individually. The upside of the field being that you have control of the archive format and/or can encrypt the archive with user specific key before sending. I researched it for an upcoming project and all the hooks are in place to create such a model and you're right, it goes beyond "batteries included". -- Melvyn Sopacua -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CA%2Bgw1GWTn%2B8f_bUV7mmJ8gEFodwUrtK_yzF_zEWA%2Bv5ew332gA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
