ARESTC / News: Recent posts

This version is a milestone as it includes threading tests that prove the robustness of ARESTConnector. It's also a milestone because the junit used has changed to 4.8.1. The latter means slowly all tests will be upgraded for the 4 version of JUnit. Please be advised that although the API has not changed a change in the behaviour has occur. The received streams are no longer transformed to the returned content type so any transformation on streams needs to occur out of ARESTC.

This release has full support for multipart and request entity submission support. It is faster than any previous and the design has finally started to be in really good shape. Check out the Website under Develop for support and don't forget to check the test cases (especially the OverallDesignTest) for real examples of what you can do.

Dear all, I see the rising interest and I feel I should warn you. The snapshots appearing from time to time are NOT nightly builds. I do not have the power to have nightly builds. I do promise though to produce a new version as fast as one is logical to be built and of course upload it. I do hope to rich a release version around October, depending on workload.

This version brings a lot of improvements and some, probably unnoticeable API changes. The improvements are mostly in performance but also in the thread safety. From now on, one instance of the connector can be used in different parts of you code. So long as the request you provide doesn't change until the connector is done with it, you should not face problems.

This version (0.1.3) is actually passing all tests and appears to work with all positive testing (clover says coverage is 79.3% with 548 / 691 elements tested ). Try it, it should not disappoint you

The new version is out with support for all methods: GET/PUT/POST/DELETE. It allows for simple requests, with body and with streamed data (binary files). see the JUnit class OverallDesignTests for examples of usage