------art_85929_15486162.1160917091941
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Currently they're only cached in memory, I could add pickle the cache to
disk on server shutdown if there is demand for it.

On 15/10/06, hemant <gethemant / gmail.com> wrote:
>
> On 10/14/06, Ian Leitch <port001 / gmail.com> wrote:
> > Hey all,
> >
> > I've just made the first release of a new project: Boogaloo.
> >
> > Boogaloo is a very simple cache server that provides persistent and
> > temporary caches. You can also use it to house your own custom services.
> > It's meant to be very simple to use so that you can concentrate on your
> > primary problem.
> >
> > You'll find it fully documented and even has a few unit tests:
> > http://boogaloo.rubyforge.org/
> > or "sudo gem install boogaloo" if you want to play straight away.
> >
> > Why?
> >
> > It started out as a place to cache my rendered Liquid template objects
> and
> > somewhere to store a list of selectors from some CSS files. Later on I
> > started using it as a temporary cache for objects that were only
> relevant to
> > specific user in Rails. So instead of keeping the object in the users
> > session and forgetting to clear it out later, I can now just stick it in
> > Boogaloo and let it expire after a period given. This is very handy for
> > multi-step forms etc.
> >
> > Anyway, I hope someone finds it useful...
> >
> > Cheers,
> > Ian.
> >
> >
>
> Interesting, so where do you cache the data that clients send you?
>
>
> --
> There was only one Road; that it was like a great river: its springs
> were at every doorstep, and every path was its tributary.
>
>

------art_85929_15486162.1160917091941--