Re: initial gencache implementation

2002-09-06 Thread Rafal Szczesniak
On Fri, Sep 06, 2002 at 10:17:19AM +1000, Tim Potter wrote: On Thu, Sep 05, 2002 at 12:15:36PM +0200, Rafal Szczesniak wrote: This is first implementation of caching mechanism. It includes both lib/gencache.c code and utils/net_cache.c as command-line control/testing tool. comments

Re: initial gencache implementation

2002-09-06 Thread Andrew Bartlett
Rafal Szczesniak wrote: On Fri, Sep 06, 2002 at 10:17:19AM +1000, Tim Potter wrote: On Thu, Sep 05, 2002 at 12:15:36PM +0200, Rafal Szczesniak wrote: This is first implementation of caching mechanism. It includes both lib/gencache.c code and utils/net_cache.c as command-line

initial gencache implementation

2002-09-05 Thread Rafal Szczesniak
This is first implementation of caching mechanism. It includes both lib/gencache.c code and utils/net_cache.c as command-line control/testing tool. comments are welcome -- cheers, ++ |Rafal 'Mimir' Szczesniak [EMAIL PROTECTED] |

gencache implementation

2002-09-05 Thread Rafal Szczesniak
I forgot to send patch with net_cache's entrypoint. -- cheers, ++ |Rafal 'Mimir' Szczesniak [EMAIL PROTECTED] | |*BSD, GNU/Linux and Samba /

Re: initial gencache implementation

2002-09-05 Thread Tim Potter
On Thu, Sep 05, 2002 at 12:15:36PM +0200, Rafal Szczesniak wrote: This is first implementation of caching mechanism. It includes both lib/gencache.c code and utils/net_cache.c as command-line control/testing tool. comments are welcome Rafal, that looks pretty good. Since you ask, I do

Re: initial gencache implementation

2002-09-05 Thread abartlet
On Fri, Sep 06, 2002 at 10:17:19AM +1000, Tim Potter wrote: On Thu, Sep 05, 2002 at 12:15:36PM +0200, Rafal Szczesniak wrote: This is first implementation of caching mechanism. It includes both lib/gencache.c code and utils/net_cache.c as command-line control/testing tool. comments

Re: initial gencache implementation

2002-09-05 Thread Tim Potter
On Fri, Sep 06, 2002 at 02:10:23AM +, [EMAIL PROTECTED] wrote: You assume that any cached data will be in null terminated string format which is not always the case. I understand this is a design property - it's up to the caller to mess with structs etc. This keeps the cache