On 7/1/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
Stephen, I think that limits as done in AS 4.5 will
not be sufficient for us. As we really do not have,
or better say, do not use the server as pure webserver.
Hence, we need the ability to set time contraints on
cache per-se and not as a pa
On 7/1/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
Am 01.07.2006 um 18:17 schrieb Gustaf Neumann:
> Zoran Vasiljevic schrieb:
>> For my *personal* taste, the API is way too large
>> but what I do not use, I do not care for.
>> I have nothing against having all this in core
>> and I have not
Am 01.07.2006 um 18:17 schrieb Gustaf Neumann:
Zoran Vasiljevic schrieb:
For my *personal* taste, the API is way too large
but what I do not use, I do not care for.
I have nothing against having all this in core
and I have nothing against maintaining this
code in future, if the need arises.
Zoran Vasiljevic schrieb:
For my *personal* taste, the API is way too large
but what I do not use, I do not care for.
I have nothing against having all this in core
and I have nothing against maintaining this
code in future, if the need arises.
The ns_cache interface resembles much similarity
Am 30.06.2006 um 21:35 schrieb Vlad Seryakov:
right
Now that we (at least Vlad an myself) have this consensus:
ns_cache_create
ns_cache_names
ns_cache_flush
ns_cache_eval
ns_cache_keys
ns_cache_get
ns_cache_set
ns_cache_append
ns_cache_lappend
ns_cache_incr
ns_cache_ex
