Introduction
This path improve overall performance of Plone. It remove opaqueitems feature from CMF (just keep talkback support)
I have discover this issue by profiling just a simple javascript file fetch throw Plone document html page and discuss it throw CMF mailing list: http://mail.zope.org/pipermail/zope-cmf/2009-August/028559.html
The result is 25% better on the total time spend in the request. Becarefull if you use a third part product that use opaqueitems and make me know if you it is, I will add it to this page. At the moment only talkback use it and are supported.
Credits
Changelog
1.1
Remove ZopeSkel stuff from egg’s metadatas [toutpt]
1.0
Remove opaqueitems (just keep talkback support)
Metadata
Release files for experimental.aggressiveopaquespeedup 1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| experimental.aggressiveopaquespeedup-1.1.zip | 14.2 kB | Without provenance | Details for experimental.aggressiveopaquespeedup-1.1.zip |
Release files / experimental.aggressiveopaquespeedup-1.1.zip
| Download URL | experimental.aggressiveopaquespeedup-1.1.zip |
|---|---|
| Size | 14.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8861c19dfd6ac422131a0e6b745e3fd502dd9176cf52c031bd1a8c2a28a117f4
|
|
BLAKE2b-256 checksum How to use checksums |
866348aaaf437d392cfc89f0f0ef42bd56f6265e25c4489829062a878617d469
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for experimental.aggressiveopaquespeedup 1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.