Anyway, it has long suffered from a problem: if the database gets big, then when a new instance of Splash! starts it has a tendency to die. This is because Spread will simply drop a client that sends messages too fast. Wrongheaded, IMNSHO, but then, Spread does a fair few wrongheaded things. As of yesterday, its fixed: what I did in the end was make the database refresh over a unicast link. The sender of the refresh forks so they don’t block, and the receiver doesn’t care about blocking, coz its dead in the water until it gets refreshed anyway.
Seems to work.
I have a long-term ambition to replace both Spread and Splash! with something much cooler. So do other people I know – but I’d love to hear from people with similar ambitions.