pulse team is preparing for the 0.8 release

2012-01-18T13:27:18Z

At the moment we are preparing ourselves for the next big release: version 0.8.

A first preview version is scheduled for the end of February.

pulse 0.7 final has been released

2010-10-26T17:51:53Z

The final release for pulse 0.7 has just been published to Sourceforge. The release is available as a binary and a source distribution.

Have fun...

pulse 0.7 RC4 has been released

2010-09-23T16:17:30Z

This version ensures compatibility with PostgreSQL and contains minor improvements in the XSLTOutputter. Moreover it improves the performance by using FastStringWriter and FastByteArrayOutputStream of the new org.torweg.pulse.util.io package throughout.

pulse RC4: PostgreSQL compatibility

2010-09-21T13:45:32Z

The upcoming fourth release candidate will ensure compatibility with PostgreSQL which is currently broken due to some strange differences between MySQL and PostgreSQL using Hibernate.
All issues will be investigated an fixed, so the final release will ensure compatibility with both MySQL and PostgreSQL.

Build failures for source distribution fixed

2010-09-20T15:40:54Z

The latest source distribution's build was broken. We have uploaded new packages with a fixed ant build and a short description on how to configure the build properties.

pulse 0.7 RC3 has been released

2010-09-15T15:55:17Z

The third release candidate addresses a bug in both AbstractSummaryDescriptionContent and AbstractSummaryDescriptionVariant concerning the site-search. It also contains a performance improvement creating a non-unique index on orderCode for StoreContent and StoreVariant.

This version is planned to become 0.7 final, if no further problems are reported.

pulse 0.7 RC2 has been released

2010-08-30T17:02:51Z

The second release candidate for pulse 0.7 has just been released. It includes a minor bugfix regarding a NullPointerException in conjunction with tampered URLs.
Alongside the fix, we also had the time to backport two features from the 0.8 development: An additional option to remove suffixes from generated Commands (which is used by the GetFullSitemap controller) and an improved EventManager implementation which is aware of the IntelliCache feature - now allowing private caching of AJAX based responses.
For more information check out the release notes: http://pulse.torweg.org/site/Pulsar/en_US.CMS.displayCMS.359./release-notes-for-0.7-rc2---changelog

pulse 0.7 Release Candidate released

2010-08-19T18:22:46Z

Finally, the release candidate for pulse has been released today.

In same run the pulse website (http://pulse.torweg.org) has been completely overhauled.

Introducing pulse IntelliCache

2010-08-13T10:35:16Z

The RC 1 of pulse (http://pulse.torweg.org) will be released within the next days introducing a powerful new caching feature called IntelliCache.

The pulse IntelliCache allows private caching of dynamic pages as long as the ServiceSession associated with the current request is still stateless. As soon as a vistor performs a stateful action such as adding an item to a shopping cart, IntelliCache switches to the non-caching mode, providing live views rendered on demand. IntelliCache is based upon ETags and can be easily set up in the ServiceRequest configuration, simply by adjusting the page validity. This way IntelliCache will always match your website's speed of change - from seconds to days.

The new feature can significantly reduce both load and bandwidth, especially on websites with a high amount of non-authenticated users. Visitors who repeatedly request pages already visited (e.g. by using the browser's back and forward buttons) are getting a vastly improved browsing experience. Our experience has been that even with moderate page validities of 10 minutes IntelliCache covers about 2% percent of the page impressions. It provides response times which are on average 10 to 50 times faster than the original requests at a minimal price - ETag calculations and validations are done in less than half a millisecond per request.

Making code even clearer

2010-04-24T21:27:04Z

The new RequestBean concept is available in the trunk.

RequestBeans are used for annotation based processing of the Parameters of a Command.

A parameter of a method annotated with either @Action or @AnyAction that is annotated with @RequestBean can have values
injected based on Command.getParameters().

The injection is controlled by the @RequestBean.Parameter annotation.

http://bit.ly/cjEppI

Recent posts to news