I've started work on a Terracotta Integration Module for Clojure already. As I understand it, we can package up the Terracotta config as well as any replacement classes. This way we can "patch" Clojure temporarily until either Terracotta supports the features we need, or Clojure can be rewritten so that it doesn't use classes that are unsupported by Terracotta (if prudent and possible), and there would be no need to fracture the Clojure code base.
I'll keep everyone apprised of my progress. Paul On Sat, Feb 28, 2009 at 11:35 PM, Nabib El-Rahman <nabi...@gmail.com> wrote: > Its a way to package integration details into a module. For example, if I > want to cluster EHCache, I can drive through the code and figure out what > data structure to share and subsequently lock on. All that work can be > packaged into a module for terracotta, so that way people who just want to > use ehcache + terracotta change just include tim-ehache in terracotta > configuration and that's it. > > the same can be done for clojure. the details can be abstract to a > tim-clojure. > > http://www.terracotta.org/web/display/docs/Terracotta+Integration+Modules+Manual > > -Nabib > > On Sat, Feb 28, 2009 at 8:16 PM, hank williams <hank...@gmail.com> wroote: >>> >>> Writing a TIM is definitely the way to go, It's a place to hide the >>> glue until both Terracotta and Clojure catches up with each other. >> >> uhhh.... what is a TIM? >> >> Thanks >> Hank >> >> >> -- >> blog: whydoeseverythingsuck.com >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
