An online demostration of active-xmlrpc 0.9.4, an open web publishing framework, running on the SandStorm platform
Aside from addition of persistent connections and registry caching for python/zope, this is mostly maintaince release when compared with 0.99
Quite a big re-write.
xmlrpc-j was replaced with Helma, as it has simpler API, and much faster according to my benchmarks.
Just released a registry implementation in Java.
It uses xmlrpc-j classes, with an addition of pure java Base64 class found on the net, so it will not depend on sun's VM internals.
It works on Kaffe VM, and can also be compiled into native executable using gcj-3.0(pre-compiled executable included, but you will need the runtime libgcj).
Starting from the next release, 0.80, SandStorm will be splited to two
packages, sstorm-lib and sstorm-core.
sstorm-lib will mainly contain the wrapper libraries used to access the
registry and modify it.
sstorm-core will contain the rest, which includes the registry, and a set of
Upcoming version of SandStorm will contain a stripped down version of the python library, which will work with Zope.
This will allow writing front-ends in Zope, using SandStorm components at the backend.
As a proof of concept, a sample Zope code that works with SandStorm::RSS will be included.
Before complaining about bugs, edit the file:
Change the line that contains:
Otherwise no stand-alone component won't work, including the registry!
This can be considered as a sub-project of SandStorm.
It uses SandStorm::RSS for getting RSS streams, without having to know what
is RSS, how to parse it, or where it is located in the net, making available
for IRC users.
So all of you geeks out there can put it in their favourite IRC channel,
asking from it to announce the latest headlines from slashdot from time to
Highlights of this release:
* cleaner and more feature-rich Ruby client code, as well as a start of a
* Sandstorm::RSS, an RSS 0.90/0.91 fetcher/parser, making the data available
via an API.
This is mostly a bugfix release
This one is really, but really bugfree! Promise!
This is a bug-fixes release.
It does not introduce new features, but mainly takes care to fix all
existing bugs, as well as make it work with win32.
Instructions for win32:
make sure python is in the path.
SandStorm::SandML 0.1 released today.
SandStorm::SandML is not a SandStorm component by itself, but it's a
framework for writing SandStorm components using an XML language named
SandML, or SML.
SandML is a programming language, with variables,type, for loops,
conditionals, and XML-RPC method calls.
Each SML file is a component, with 0 or more methods, each of them can
types are most native XML-RPC types... read more
SandStorm is creating lots of interest in the Open Source community, and the
statistic prove it(Project activity is on the top 100 for several days).
There is one problem which seems to be common. People find it hard to
install and configure.
I admin, I often release tarballs without checking them first on a clean
This is will not be the case from SandStorm 0.61 (Code named "Dusty sky").... read more
Not many changes, but major ones:)
Includes a stand-alone registry, a fast replacement for the CGI one that existed till now.
stand-alone components are now in CVS.
Both tar/gzip and tar/bzip2 forms are available.
enhancement to SandStorm::Mail component.
New component, SandStorm::Public. acts as a proxy to the rest of components, restricting access via ACL mechanism
There is a bug in setup/registry.py file in SandStorm 0.55 that makes it generate bad Registry file.
You can either edit the files manually, or download the fixed registry.py from the download page.
This release mostly includes bug fixes, as well as a start of a Mail component
SandStorm's website lanuched today.
It is currently quite minimal though.
Changes include a Mirror component, CGI active.notify Component, and new setup utility
The .htaccess file generated by SandStorm 0.50 does not work well with mod_python and mod_perl.
To make it work with mod_perl, SetEnv PERL5LIB directive has to be added.
PythonPath directive should be set in mod_python.