[Mason-devel] making CHI the cache default

Discussion:

Jonathan Swartz

2009-12-29 15:26:13 UTC

In the next release I'd like to make CHI the cache default, and
removing the dependency on Cache::Cache. To use caching, one will have
to explicitly install CHI (or Cache::Cache if one really desires).

This is mainly so that new users of Mason aren't defaulted into a
moribund caching system.

Any objections?

Jon

Dave Rolsky

2009-12-29 16:06:29 UTC

Permalink

Post by Jonathan Swartz
In the next release I'd like to make CHI the cache default, and
removing the dependency on Cache::Cache. To use caching, one will have
to explicitly install CHI (or Cache::Cache if one really desires).
This is mainly so that new users of Mason aren't defaulted into a
moribund caching system.
Any objections?

Are you saying we wouldn't depend on either? Can we depend on CHI
explicitly? I want caching to be available for anyone who installs Mason.

-dave

/*============================================================
http://VegGuide.org http://blog.urth.org
Your guide to all that's veg House Absolute(ly Pointless)
============================================================*/

Jonathan Swartz

2009-12-29 16:22:13 UTC

Permalink

Post by Dave Rolsky

Are you saying we wouldn't depend on either? Can we depend on CHI
explicitly? I want caching to be available for anyone who installs Mason.

Jonathan Swartz

2009-12-29 16:30:59 UTC

Permalink

CHI is the next generation of Cache::Cache.

http://search.cpan.org/~jswartz/CHI-0.33/lib/CHI.pm

That's fine, I'll leave things as is, and wait for Mason 2 to default
to CHI. :)

Jon

If I get a vote, then I agree caching should work out of the box.
And I don't really want extra dependencies right now - my customer
base has a hard enough time installing the modules we already require.
Forgive my ignorance, but what is CHI?

Post by Jonathan Swartz

Post by Dave Rolsky

Are you saying we wouldn't depend on either? Can we depend on CHI
explicitly? I want caching to be available for anyone who installs Mason.

CHI has a whole lot of dependencies, particularly Moose, that Mason
doesn't have right now and that I don't want to add.
You make a good point, it is nice for caching to work out of the box.
Maybe I'll just leave this as is and ratchet up the mentioning of CHI
in the docs.
Jon
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast
and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Mason-devel mailing list
https://lists.sourceforge.net/lists/listinfo/mason-devel

--
Shane P. McCarron Phone: +1 763 786-8160 x120
Managing Director Fax: +1 763 786-8180

Shane McCarron

2009-12-29 16:24:35 UTC

Permalink

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
If I get a vote, then I agree caching should work out of the box.  And
I don't really want extra dependencies right now - my customer base has
a hard enough time installing the modules we already require.  
 
Forgive my ignorance, but what is CHI? 
 
Jonathan Swartz wrote:
<blockquote cite="mid:A4A7CDEF-8F48-4C09-9300-***@pobox.com"
type="cite">
<blockquote type="cite">
<pre wrap="">On Tue, 29 Dec 2009, Jonathan Swartz wrote:

</pre>
<blockquote type="cite">
<pre wrap="">In the next release I'd like to make CHI the cache default, and
removing the dependency on Cache::Cache. To use caching, one will
have
to explicitly install CHI (or Cache::Cache if one really desires).

This is mainly so that new users of Mason aren't defaulted into a
moribund caching system.

Any objections?
</pre>
</blockquote>
<pre wrap="">Are you saying we wouldn't depend on either? Can we depend on CHI
explicitly? I want caching to be available for anyone who installs
Mason.

</pre>
</blockquote>
<pre wrap="">
CHI has a whole lot of dependencies, particularly Moose, that Mason
doesn't have right now and that I don't want to add.

You make a good point, it is nice for caching to work out of the box.
Maybe I'll just leave this as is and ratchet up the mentioning of CHI
in the docs.

Jon

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
<a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/verizon-dev2dev">http://p.sf.net/sfu/verizon-dev2dev</a>
_______________________________________________
Mason-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Mason-***@lists.sourceforge.net">Mason-***@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/mason-devel">https://lists.sourceforge.net/lists/listinfo/mason-devel</a>
</pre>
</blockquote>
 
<pre class="moz-signature" cols="72">--
Shane P. McCarron Phone: +1 763 786-8160 x120
Managing Director Fax: +1 763 786-8180
ApTest Minnesota Inet: <a class="moz-txt-link-abbreviated" href="mailto:***@aptest.com">***@aptest.com</a>

</pre>
</body>
</html>