So I'm a bit late to the party, and only now have noticed that there's something called Spread (http://www.spread.org) from Ask Bjorn Hansen's presentation slides.
The documentation for spread seems to be er, lacking. I can think of ways to use it but first of all? How widely is it being used? What do YOU use it for?
The other thing: Which perl binding do you use? Spread.pm and Spread::Session looks ok, but my immediate response was, oh, why don't I write Spread::libspread (much like Memcached::libmemcached) and make it pure OO to start with? Bad idea?
In any case, I'm interested in knowning what/how Spread is being used.... anybody?
So
acme on 2008-04-23T09:23:19
I've played with Spread over the years. In my experience, it will not do what you want it to do. mod_log_spread is about all you should use it for.
Leon
Re:So
jplindstrom on 2008-04-23T12:31:32
So what are some potential alternatives that does do what you want it to do?
I've been where it was used
btilly on 2008-04-23T10:38:55
They used it for several years at Rent.com to make sure that uploaded images were copied to all of the webservers. I never had to work with it, but my impression was that it was somewhat finicky, but got the job done.
I don't know if they're still using it.
For most need to establish a shared state we used data in databases or caches using memcached. We ran into one major bug, a buffer overflow if your keys were too long. We handled that by taking an MD5 hash of the key we wanted to use, thereby guaranteeing that our key was always short. Other than that bug, memcached rocked.