We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
as @giorrrgio and @agiuliano suggested, now that we have http-caching #18, we should care about the Packagist Api.
I profiled the application (and the filesystem is so fast compared to the request/response).
Maybe could be great use the LiipCacheBundle in order to store the packagist request/response.
Other ideas? any other that profiled the application? anyone who wants to do this cool task?
cool
The text was updated successfully, but these errors were encountered:
sorry I miss this is closed 3 or 4 months ago.
Sorry, something went wrong.
No branches or pull requests
as @giorrrgio and @agiuliano suggested,
now that we have http-caching #18,
we should care about the Packagist Api.
I profiled the application (and the filesystem is so fast compared to the request/response).
Maybe could be great use the LiipCacheBundle in order to store the packagist request/response.
Other ideas? any other that profiled the application? anyone who wants to do this
cool
task?The text was updated successfully, but these errors were encountered: