v2

[RWOverdijk]

This is a general discussion for AssetManager V2. We'll be collecting things to be done and discuss them as well.

• Last modified Return 304 code during a hour #130
• @iwalz collection Static references / Browser caching #75
• Cache warmup Cache warmup / renewal #40
• Static file cache revisit static file cache. #76
• Serving collections and naming of config keys Serve collections without serve single files #102
• Serving hash-based [Question] How to serve file hash #99
• Safe names (is this actually an issue?) Missing rawurldecode() #107
• Better filters Extension-based filters not working as expected #109
• Filters and collections A Collection of .less files is compiled file by file, but should be compiled concatenated #110
• Resolvers shouldn't implement setAggregateResolver
• CDN / publish assets Publish assets #131
• Wildcard cache Is it possible to do wildcard caching? #121
• Wildcards in general

[RWOverdijk]

@Ocramius this is just open-discussion for now. Let's see what we can add to / remove from the list.

[wshafer]

@RWOverdijk - I have a quick question on the cache warmup. It seems that everything is already in the config. Wouldn't the warm up simply be go through the config, if caching is set on those, dispatch all the assets and let the current functionality take care of generating the cache? The ticket itself says to visit the URL's but it seems that we could simply dispatch the asset per the config and let the existing system handle all the hard work.

[RWOverdijk]

@wshafer Not really. I base this on the use-case we have for this module, where the asset's path (base) depends on the url. There are multiple lookup paths, and we change the request accordingly. So, the url etc in fact do matter. Also, for paths, it's impossible to warmup the files you want to use. We don't know which files that are.

[dready]

is there some kind of update due to the state on this? also is there a roadmap?

We really need the last modified handle and i am not sure if it's wise to hold all updates to the project until v2 is released. I have the bad feeling that the v2 is taking forever and getting to much weight...

don't want to step on any toes, just my thoughts, great work anyway, thx!

best regards

[Ocramius]

@dready nothing going on here for now. 1.x is very very (VERY! I mean it, seriously!) stable, and upgrading to 2.x when it's out shouldn't mean "rewrite everything" anyway.

[RWOverdijk]

What he said. Although, if there are absolute must-haves to make life a lot easier I'd be more than willing to hear from you.

[spiffyjr]

I didn't see this on your check list but a nice way to manage debug mode which removes filters and expands collections would be nice. That would require some sort of view helper, I think, so that when you output a collection in debug mode it really includes multiple script lines.

[RWOverdijk]

@spiffyjr You'd use your local config for that.

[wshafer]

Ok I've gone through all the issues in the repo and what's on this list and created a list of things I'm willing to tackle for a V2.

Please take a look and let me know if this list is adequate and if there's anything else you'd to see added.

https://github.com/wshafer/assetmanager-core/issues?utf8=%E2%9C%93&q=is%3Aissue

@RWOverdijk

[RWOverdijk]

@wshafer Comprehensive and contains the most important tasks in my opinion. 👍

[RWOverdijk]

There's a v2 now, because Laminas.

Let's at least close this.