Re: [Components] Cache: Design for hierarchical caching

2008-04-16 Thread Derick Rethans
On Thu, 10 Apr 2008, Tobias Schlitt wrote: On 04/10/2008 09:59 AM Derick Rethans wrote: On Wed, 9 Apr 2008, Tobias Schlitt wrote: On 04/09/2008 02:13 PM Derick Rethans wrote: Sometimes you might not want the items stored in a higher stack level, for example because of data size

Re: [Components] Cache: Design for hierarchical caching

2008-04-16 Thread Derick Rethans
On Mon, 14 Apr 2008, Tobias Schlitt wrote: On 04/07/2008 09:25 PM Tobias Schlitt wrote: I just finished a the first draft of my design for hierarchical (multi level) caching in the Cache component. Please take some minutes and review my proposal. You can find the RST in SVN under

Re: [Components] Cache: Design for hierarchical caching

2008-04-16 Thread Tobias Schlitt
Hi! On 04/16/2008 07:49 PM Derick Rethans wrote: On Thu, 10 Apr 2008, Tobias Schlitt wrote: On 04/10/2008 09:59 AM Derick Rethans wrote: On Wed, 9 Apr 2008, Tobias Schlitt wrote: On 04/09/2008 02:13 PM Derick Rethans wrote: Sometimes you might not want the items stored in a higher stack

Re: [Components] Cache: Design for hierarchical caching

2008-04-16 Thread Derick Rethans
On Wed, 16 Apr 2008, Tobias Schlitt wrote: On 04/16/2008 07:49 PM Derick Rethans wrote: The problem of having a dedicated storage stack is that the application then needs to start caring about in which storage stack to store a specific file. I think you might be missing that I meant

Re: [Components] Cache: Design for hierarchical caching

2008-04-16 Thread Tobias Schlitt
Hi! On 04/16/2008 08:05 PM Derick Rethans wrote: On Mon, 14 Apr 2008, Tobias Schlitt wrote: On 04/07/2008 09:25 PM Tobias Schlitt wrote: Some minor comments: Replacement strategies -- [snip] A problem with any of the replacement strategies is, that additional

Re: [Components] Cache: Design for hierarchical caching

2008-04-16 Thread Tobias Schlitt
Hi! On 04/16/2008 08:41 PM Derick Rethans wrote: On Wed, 16 Apr 2008, Tobias Schlitt wrote: On 04/16/2008 07:49 PM Derick Rethans wrote: The problem of having a dedicated storage stack is that the application then needs to start caring about in which storage stack to store a specific

Re: [Components] Cache: Design for hierarchical caching

2008-04-16 Thread Thomas Nunninger
Hi, I see your problem. However, you should not cache PDF files in memory anyway, but store them somewhere as PDF files and link to them. Reading a 100 MB PDF through PHP is overhead in itself, so you would not want to use Cache here anyway. That's just your opinion on this, and

Re: [Components] Cache: Design for hierarchical caching

2008-04-16 Thread Thomas Nunninger
Hi, It needs to be clearified, if restored items should be bubbled up to higher storages. Why wouldn't we want that? Because it costs time again. Imagine a 4 level stack, where file system is the lowest and largest one. Each time an item would be restored from the there, it

Re: [Components] Cache: Design for hierarchical caching

2008-04-16 Thread Gaetano Giunta
Thomas Nunninger a écrit : Hi, I see your problem. However, you should not cache PDF files in memory anyway, but store them somewhere as PDF files and link to them. Reading a 100 MB PDF through PHP is overhead in itself, so you would not want to use Cache here anyway. That's just