#1140: Fragment-Cache may generate too large filenames
--------------------------------------+-------------------------------------
Reporter: fnordf...@… | Owner: david
Type: enhancement | Status: closed
Priority: normal | Milestone: 1.0.2
Component: filter | Version: 1.0.1
Severity: normal | Resolution: wontfix
Keywords: Fragment-Cache | Has_patch: 0
--------------------------------------+-------------------------------------
Changes (by david):
* status: new => closed
* resolution: => wontfix
Comment:
Marking as wontfix.
Reasons:
1. it worsens the problem on Windows systems where the combined maximum
path length is 255 characters (this is a Windows API limitation)
1. the hashes are not reversible
1. you may use the following workarounds:
1. override the {{{AgaviExecutionFilter::*Cache()}}} methods
1. use cache group callbacks (see #854) to normalize the group parts to
shorter values (that would be my recommendation); you can also use them to
combine several variables into one value to have fewer permutations of a
cache
We might add some kind of logging in Agavi 1.2 if file-based storages are
trying to store to such a filename on a system affected by one of the
limitations.
--
Ticket URL: <http://trac.agavi.org/ticket/1140#comment:2>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
