phpgroupware-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [phpGroupWare-developers] caching static data


From: Dave Hall
Subject: Re: [phpGroupWare-developers] caching static data
Date: Fri, 16 Nov 2007 15:58:54 +1100

On Thu, 2007-11-15 at 20:58 +0100, Sigurd Nes wrote:
> Hi all,
> 
> We have a caching feature based on shm in API which in most cases is working 
> well.
> In some cases it can't be used - and I propose to add a caching-table to hold 
> compiled and static data which should survive a reboot.
> This could be acl-userlists per location, generated queries and things like 
> that.
> 
> I have used this approach in the app property - but I also think that ACL 
> could benefit from it when shm is not an option
> 
> schema:
> 'phpgw_cache' => array(
>   'fd' => array(
>     'name' => array('type' => 'varchar','precision' => '50','nullable' => 
> False),
>     'value' => array('type' => 'text','nullable' => True)
>   ),
>   'pk' => array('name'),
>   'fk' => array(),
>   'ix' => array(),
>   'uc' => array()
> ),
> 
> Any thoughts ?
> Where should it be placed ?

Why not use the existing appsession data table?  It can be cached in
there.  Just set the owner to something obvious like -1 (use a class
constant for it).  Add the code to the abstract session class to support
it.

I don't think we need another table for this.

Cheers

Dave
-- 
Dave Hall (aka skwashd)
API Coordinator
phpGroupWare
e address@hidden
w phpgroupware.org
j address@hidden
sip address@hidden
       _            ____                    __        __             
 _ __ | |__  _ __  / ___|_ __ ___  _   _ _ _\ \      / /_ _ _ __ ___ 
| '_ \| '_ \| '_ \| |  _| '__/ _ \| | | | '_ \ \ /\ / / _` | '__/ _ \
| |_) | | | | |_) | |_| | | | (_) | |_| | |_) \ V  V / (_| | | |  __/
| .__/|_| |_| .__/ \____|_|  \___/ \__,_| .__/ \_/\_/ \__,_|_|  \___|
|_|         |_|                         |_|Web based collaboration platform






reply via email to

[Prev in Thread] Current Thread [Next in Thread]