I've answered this email in the past, but sourceforge's mailing lists
seems to be screwed up a bit lately:)
> expandable. So far our only solution was to just throw meatier hardware at it.
> And maybe round robin the dns to a couple of front end apache machines. Not
> real sure just yet of what we will gain by going with SandStorm, but the ideas
> of colo-ing front end machines where we need them, and reusing our backend
> sounds really cool.
Yes, that is the intention behind SandStorm, make things more
distributed, cross-language, and seperate the interface from the
I started SandStorm actually as an attempt to re-write a web publishing
system, "active"(which currently powers most "indymedia" sites), in a
more scaleable and modular way.
I created an API to the database, accessable as PHP SandStorm component,
ripped off the DB code from the front-end, and replaced it with the
XML-RPC calls, and the file-based caching mechanism was replaced by
smart cache-on-demand-flush-on-update type of cache policy via the
> Sstorm-discuss mailing list
Get latest updates about Open Source Projects, Conferences and News.