Handling of families of bundles - Githubissues

jaylett / django-and-pipelines

We'll come up with a better name later

6 stars 0 forks source link

Handling of families of bundles #5

Open rbarrois opened 8 years ago

rbarrois commented 8 years ago

A user might want to split a same bundle in different ways:

A non-minified, non-concatenated version for development
A heavily concatenated version for HTTP/1 clients
A minified, split version for HTTP/2 clients (more efficient)

How do we allow this feature — do we even want to?

Support for many assets sections in the manifest file
- pros: a single manifest file
- cons: more complex format
Advise the user to generate several manifest files, one per target
- pros: maps easily onto common pipeline designs (one top-level task per target → each generates its manifest)
- cons: makes the job harder for the web framework: must be able to load more than one manifest file and to route accordingly

I'd go for option 2: keeps the format simple and allows for more customization in the future.

jaylett commented 8 years ago

Option 2. Possibly with advice that for HTTP 1.1 vs 2 it might be worth having different bundles in the same manifest, with the framework choosing automatically. (If it can. I don't think there's any consistency about how protocol version is passed across from the web server, or even if it is.)