There are agents, atoms, vars, seqs, and lisp macros all of which may make
Clojure a more appealing alternative to Java for use with Terracotta.
My goal was to get Clojure working with Terracotta, period. Most of the work
I did was actually focused on vars so that you could define a function
Hi Chas,
if you want to 'spawn' independent processes over different machines,
terracotta could be an option. But as soon as these processes are
going to share state, it gets a lot more complicated since a scalar
clock MVCC based stm is not going to be scalable over different
machines.
Afaik
I can't respond to that, but presumably these issues are irrelevant if
one were using terracotta to coordinate asynchronous independent
computation, e.g. using agents heavily?
- Chas
On Jul 16, 2010, at 8:00 AM, peter veentjer wrote:
To repeat myself again:
The big problem with a MVCC
broken failure atomicity (since some of
them only
guarantee atomicity over a single 'record' and not over records
spanning
multiple machines that are modified in a single transaction.
On Jul 16, 4:51 am, Alex Miller alexdmil...@yahoo.com wrote:
Hi,
I used to be a tech lead at Terracotta but I am now
Hi --
I'm noob to both Clojure and Terracotta but if you're willing to
tolerate basic questions from me, I'd be very interested in helping
out.
On Jul 12, 3:36 am, peter veentjer alarmnum...@gmail.com wrote:
I don't think it every is going to scale.
MVCC/TL2 based STM designs rely
If anyone is interested, the latest version of my terracotta TIM is at
http://github.com/pjstadig/tim-clojure-1.0.0 and it tries to be a Clojure
1.0.0 compatible TIM, which shows how its a bit out-of-date.
I am very open to collaboration, and I would love pull requests, or any
patches that anyone
Hi,
I used to be a tech lead at Terracotta but I am now a full-time
Clojure dev. I think it would be very interesting to explore the new
Terracotta Toolkit product to provide a distributed store for Clojure
data structures. I think it actually comes out in GA next week
although it's been
I have not pursued any further work with Terracotta, because I haven't had a
real project that required it. I'd be glad to try to pick something back up,
especially if there are others interested in helping out.
Paul
http://paul.stadig.name/ (blog)
703-634-9339 (mobile)
pjstadig (twitter)
p
on a central mechanism.
On Jul 11, 6:50 pm, scx mark_addle...@bigfoot.com wrote:
hi --
i've seen paul standig's work with clojure + terracotta. wondering if
anyone has continued his work?
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group
hi --
i've seen paul standig's work with clojure + terracotta. wondering if
anyone has continued his work?
--
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
Note that posts from new members
I've been following this too, and have not heard anything in a while. I
know that Luc Prefontaine was trying to get terracotta to work with Clojure
as well. I have not heard any news recently. A potentially more
straightforward solution for distributed processing right now is swarmiji
that's too bad. i'm actually more interested in terracotta as a
persistence solution than as a distributed computing solution.
On Jul 11, 9:02 pm, rob levy r.p.l...@gmail.com wrote:
I've been following this too, and have not heard anything in a while. I
know that Luc Prefontaine was trying
Maybe terrastore would be a good solution then?
http://clojars.org/search?q=terrastore
http://github.com/sbtourist/terrastore-cloj
On Sun, Jul 11, 2010 at 10:10 PM, scx mark_addle...@bigfoot.com wrote:
that's too bad. i'm actually more interested in terracotta as a
persistence solution than
P.
rob levy r.p.l...@gmail.com wrote ..
I've been following this too, and have not heard anything in a while. I
know that Luc Prefontaine was trying to get terracotta to work with Clojure
as well. I have not heard any news recently. A potentially more
straightforward solution
Sounds interesting! Thanks.
Hope to look at it when I have more time in my hands.
On Thu, Dec 10, 2009 at 1:37 PM, Paul Stadig p...@stadig.name wrote:
There is a new repo at http://github.com/pjstadig/tim-clojure-1.0.0/
that has a 1.0 compatible version of the TIM. It should be simpler to
Hey everyone,
I haven't been in #clojure that often lately, but when I have been
there were people asking about Terracotta integration on two separate
occasions. What are the chances of that?! :)
There is a new repo at http://github.com/pjstadig/tim-clojure-1.0.0/
that has a 1.0 compatible
it work there.
Yes, I can try to help. Feel free to write me.
Actually, I would like to try Clojure + Terracotta as a data layer for
my Java app, so I'm more interested in adapting the changes to the
latest Clojure codebase and tuning Terracotta interaction. I saw
autolocking in config and now
Thanks for your feedback.
I was able to get it to work again and pushed some minor changes to
the git repo. I downloaded Terracotta 3.1.1, and followed the
instructions in the tim-clojure-1.0-SNAPSHOT/example/README. I ended
up uncommenting all of the code in ClojureTerracottaConfigurator.java.
I
Hi Paul,
the code from [1] does not work under the latest Terracotta (3.1.1)
with clojure-slim.jar's in the following combinations:
1) branch 1.0.x from [3]
2) branch 1.0.x from [3] + modified
ClojureTerracottaConfigurator.java (uncommented lines)
3) [2] svn revision 1335 + modified
Hey Sergey,
I did the work on the Clojure TIM. I published a report of my findings at
[1]. At least three of the roadblocks that I encountered were fixed in
Terracotta 3.0.1 [2].
I believe the TIM works with Clojure 1.0, but it's been several months since
I've looked at the code. There are still
thread Clojure + Terracotta Update and it
looks pretty positive.
A few question for TIM users:
Is there newer version than
http://github.com/pjstadig/tim-clojure-1.0-snapshot ?
Are there still bugs?
Can it be called production ready?
Regards, Sergey.
--
You received this message because
Thanks for your answer, Paul!
I'm certainly going to try this TIM.
Another question:
You say that it requires runtime replacement of some Clojure classes
but the lines that include modified *TC.java files are commented ( see
ClojureTerracottaConfigurator.java from tim-clojure-1.0-snapshot
).
Hi from a Clojure newbie!
I have read the april thread Clojure + Terracotta Update and it
looks pretty positive.
A few question for TIM users:
Is there newer version than
http://github.com/pjstadig/tim-clojure-1.0-snapshot ?
Are there still bugs?
Can it be called production ready?
Regards
I've been speaking with the Terracotta engineers, so here is an update on a
couple of the issues:
1) array.clone(). It turns out this is a bug in Terracotta. They have
acknowledged it, and will be working to resolve it. However, they mentioned
(as I have found else where on the interweb[1][2
You're doing amazing work! I look forward to the result.
On Thu, Apr 2, 2009 at 5:37 PM, Paul Stadig p...@stadig.name wrote:
I've been speaking with the Terracotta engineers, so here is an update on a
couple of the issues:
1) array.clone(). It turns out this is a bug in Terracotta
On Mar 30, 5:12 pm, Paul Stadig p...@stadig.name wrote:
I have gotten to the point in my Clojure + Terracotta experiment, where I
believe all of the features of Clojure are functional (Refs, Atoms,
transactions, etc.). I do not have a way to extensively test the Clojure
functionality, but I
On Mar 5, 4:23 pm, Paul Stadig p...@stadig.name wrote:
I had one last, major hurdle, and was helped by Chouser (thank you!).
http://paul.stadig.name/2009/03/clojure-terracotta-we-have-repl.html
Still lots more to do, and probably some simple changes that could be
rolled back
I had one last, major hurdle, and was helped by Chouser (thank you!).
http://paul.stadig.name/2009/03/clojure-terracotta-we-have-repl.html
Still lots more to do, and probably some simple changes that could be
rolled back into the Clojure codebase. However, I feel as though I've
finally reached
On Mar 5, 12:23 pm, Paul Stadig p...@stadig.name wrote:
I had one last, major hurdle, and was helped by Chouser (thank you!).
http://paul.stadig.name/2009/03/clojure-terracotta-we-have-repl.html
Still lots more to do, and probably some simple changes that could be
rolled back
I've done some more work on Clojure + Terracotta. I moved my code into
a Terracotta Integration Module (TIM), which allows the bundling and
reuse of the Terracotta configuration, but also provides for class
replacement so that clustered versions of some classes can be written
without necessarily
- and
the clojure/terracotta topic is of interest to a lot of people...
It would be wonderful if someone would come and talk about the
progress...
Regards,
Amit.
http://www.meetup.com/The-Bay-Area-Clojure-User-Group/
On Mar 1, 8:37 am, Luc Prefontaine lprefonta...@softaddicts.ca
wrote:
We
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
We will go for a TIM. Just looked at the doc and tes that would simplify
our work a lot.
Thank you,
Luc
On Sat, 2009-02-28 at 18:48 -0800, Nabib El-Rahman wrote:
Hi guys,
I work for Terracotta ( on the server side ) and find this work with
Clojure + Terracotta very exciting. Writing
Are any of the folks on this thread in/around the bay area? (I know
Nabib is).
We're having a clojure user-group meeting on the 12th of March - and
the clojure/terracotta topic is of interest to a lot of people...
It would be wonderful if someone would come and talk about the
progress...
Regards
of the folks on this thread in/around the bay area? (I know
Nabib is).
We're having a clojure user-group meeting on the 12th of March - and
the clojure/terracotta topic is of interest to a lot of people...
It would be wonderful if someone would come and talk about the
progress...
Regards,
Amit
My approach was just to share what few refs I wanted, but another
approach (like Luc's) is to share everything. The obvious advantage
being that you can set! the root binding of vars (like function
definitions). The goal with Terracotta is to make things as
transparent as possible, so I don't
Terracotta will provide instrumentation on
this class
by default so the shared implementation could be thrown away in the
near future.
We see the double implementations as a transition period until
Terracotta supports
it directly.
2) Noted
Shared versus local mode:
That's what we have in mind, getting
In the Namespace case, it might be premature optimization to worry
about AtomicReference being replaced. If there is a way to rewrite
that code with, say, synchronized blocks, and it will work better with
Terracotta, I think it would be worth doing. I don't think it would be
normal usage
We think the same way. Our first implementation of an alternative to
AtomicReference
is straightforward, we will look at improving it if the need arises.
It will be easier to do so when we get stats from Terracotta after
running some benchmarks.
There's much to do before getting there.
Luc
Hi guys,
I work for Terracotta ( on the server side ) and find this work with Clojure
+ Terracotta very exciting. 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. If you have any questions feel free to post
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
I've recently done some experimentation with Clojure and Terracotta.
I've detailed my experience at:
http://paul.stadig.name/2009/02/clojure-terracotta-yeah-baby.html
and shared my code at:
http://github.com/pjstadig/terraclojure/tree/master/
I'm the first to admit that I'm not an expert
We are trying to get Clojure shared over Terracotta, not just specific
things but the whole Clojure object space
(name spaces, root values, ) except stuff that needs to remain local
(streams, ).
We take an all or nothing approach here, we would to see many Clojure
instances work
Paul Stadig p...@stadig.name writes:
I've recently done some experimentation with Clojure and Terracotta.
I've detailed my experience at:
http://paul.stadig.name/2009/02/clojure-terracotta-yeah-baby.html
Very exciting; I'm looking forward to trying this out! Thanks for posting.
-Phil
of
the clients.
And as I said in my article, I didn't do any work with agents, so
maybe there's a lot missing from my part of the puzzle.
Paul
On Fri, Feb 27, 2009 at 4:37 PM, Luc Prefontaine
lprefonta...@softaddicts.ca wrote:
We are trying to get Clojure shared over Terracotta, not just specific
are trying to get Clojure shared over Terracotta, not just specific
things but the whole Clojure object space
(name spaces, root values, ) except stuff that needs to remain local
(streams, ).
We take an all or nothing approach here, we would to see many Clojure
instances work
this step, real fun will begin, right now were having only an
appetizer...
Luc
It would be great if you could mention the difficulties you face as
you go, before you spend too much time on workarounds. I am interested
in seeing Clojure on Terracotta and if there are things I can do
easily
the Clojure run time will need more
thinking and
there might be other ways to do work around these issues.
I can post an update each 2 weeks or so or on demand before we spit out
code
if we face an issue.
Right now we are busy writing a tool in Clojure to generate the
terracotta configuration
from
of an immutable data structure that won't be an issue. Sorry
for the confusion...
Alex
On Oct 19, 7:07 pm, Alex Miller [EMAIL PROTECTED] wrote:
Rich, I'm the tech lead for the transparency team at Terracotta and
this is not exactly correct. For example, while you can read
clustered state outside
that you can get dirty reads in this scenario but in
the case of an immutable data structure that won't be an issue. Sorry
for the confusion...
Thanks for the clarification - that's great news. I remember that
being the answer when I first researched Terracotta.
Rich
On Oct 19, 7:07 pm, Alex
Rich, I'm the tech lead for the transparency team at Terracotta and
this is not exactly correct. For example, while you can read
clustered state outside of a clustered lock, it's possible for the tc
memory manager to clear that state at any time, allowing you to see a
null instead of the real
On Fri, Oct 17, 2008 at 8:01 PM, Luc Prefontaine
[EMAIL PROTECTED] wrote:
I am not very far from tackling this issue. In our bus messaging system, we
are using Terracotta with some Java components
and it's a matter of weeks before we start to investigate how we can bridge
Clojure
you,
Luc
On Sat, 2008-10-18 at 08:50 -0400, Rich Hickey wrote:
On Fri, Oct 17, 2008 at 8:01 PM, Luc Prefontaine
[EMAIL PROTECTED] wrote:
I am not very far from tackling this issue. In our bus messaging system, we
are using Terracotta with some Java components
and it's a matter of weeks
53 matches
Mail list logo
