Besides the obligatory bugfixes, we have also some nice new features in this new version. They mainly concern the web modules (Investigator and Vizard) and and Shell.
We are currently heavily working on the proper documentation of our code. We are almost finished, so you can already find Javadoc in most of the code. Especially in IDEs this should be very handy to have the doc right at hand.
We also added a new section to this page called "Showcases". Here we will put some nice code examples and videos to give visitors an impression of the SQLSpaces power without reading documentation first ... Check it out!
Finally, we added another new section called "Testimonials", where we will collect experiences of other SQLSpaces users.
New Features
Bug Fixes
This time, we put a small christmas service release under the christmas tree. Its main focus lies on fixing two severe bugs.
An important thing to notice is that the configuration file has slightly changed: Previously there were keys like "db.mysql.host" or "db.mysql.port". These are now called "db.host" or "db.port" and also affect the PSQL configuration. The previous keys are still being interpreted, but are deprecated and support for them will be removed in one of the next versions!
Bug Fixes
And here comes another new version of the SQLSpaces. As always it is completely backwards compatible, so you can just replace the jars and everything should (!) work ;-) For now, we have decided to call this version 3.9 and not 4.0, because it is more of a evolution than a revolution. So be prepared for a great, new, shiny and innovative version 4.0! (And if you have any ideas what we could improve/extend, just drop us a mail!)
New Features
For experienced users we introduced a bash-like shell to easily investigate and change the state of the server. Look at the documentation of the sssh to learn more about it.
In case you are dealing with real huge amounts of data, you can now use new query commands that are especially designed for this case. Normally, the returning tuple in the read and take case is randomized if there is more than one match. Now you can use readFirst or takeFirst to skip this randomization. Moreover, if you are not interested in the content of a tuple, you can use delete/deleteFirst/deleteAll instead of take and you can use count instead of readAll if you just want to know the amount of matches. Large amounts of tuples (or large tuples) are then processed much faster.
The TupleSpace class now has import and export methods to dump and reinsert all tuples of one space into/from files. This can be used to easily copy the contents of a space from one server to the other. This functionality will probably be also available from the Investigator in the next version.
If you are using SQLSpaces in a scientific context, we compiled a list of our publications so that you can easily cite them. Moreover, there you can look at our previous usage scenarios.
Bug Fixes
Again, this version is completely backwards compatible and contains bugfixes and performance enhancements. The main focus this time lies on the handling of large amounts of data.
New Features
The querying of the database has been completeley exchanged. Especially if you have readAll or takeAll queries that return more than 500.000 tuples, the SQLSpaces server works more memory-efficient and faster by splitting up the SELECT into several SELECTs with LIMITs.
If you have readAll with many results and don't want to blow the memory, you can now use the new readAll(Tuple t, int windowsize) method that returns an iterator (compatible with for-each). This iterator uses the given window size to successively fetch the results from the server.
HSQLDB support was moved to from version 1.8 to 2. MySQL connector was updated.
There are many new localizations for the web-interface.
Bug Fixes
This version is completely backwards compatible and contains quite some bugfixes for critical problems, so we highly recommend to update.
New Features
Now they don't use internal VM calls anymore, but the so-called remote-admin channel. That way they can be deployed in a tomcat without the need for a shared Java memory.
The code for the client was adapted so that it now also runs on the android platform. No further jars needed, just use the default sqlspaces-client and -commons jar. Successfully tested on HTC Dream and HTC Magic.
The XML protocol can now also be tunneled over XMPP. Just configure SQLSpaces and the XMPP server and put the new XMPP-Jars in the classpath.
The Vital Signs Monitor is a background thread that regularly checks important values of the server like: amount of database connections and SQLSpaces connections, memory usage, internal locks, etc.
This new field type enables you to specify tuple templates with fields that should not match a certain string.
Bug Fixes