Skip to content

Releases: diennea/blazingcache

v3.4.0

20 Mar 11:33

Choose a tag to compare

What's Changed

v3.3.1

12 Nov 10:47

Choose a tag to compare

  • fixed a bug in the ssl configuration

v3.3.0

10 Jan 11:56

Choose a tag to compare

  • fixed a bug in the invalidation flow
  • updated some libraries (most notably, jcache from 1.1.0 to 1.1.1)
  • fetch requests are distributed among same-fetch-priority clients (if multiple same-fetch-priority clients are holding the requested key)

v3.2.0 [DO NOT USE]

08 Jan 19:06

Choose a tag to compare

v3.2.0 [DO NOT USE] Pre-release
Pre-release
  • fixed a bug in the invalidation flow
  • updated some libraries (most notably, jcache from 1.1.0 to 1.1.1)
  • fetch requests are distributed among same-fetch-priority clients (if multiple same-fetch-priority clients are holding the requested key)
  • upgraded target jdk version to 17

v3.1.0

29 Aug 18:08

Choose a tag to compare

  • Thinned the payload of 'Load' requests from the cache-client. Cache value is no longer sent to server (it was not used). No behaviour changes

V3.0.0

16 Aug 08:35

Choose a tag to compare

This release contains a bug-fix for the cache-client. This fix could highlight issues in your application's invalidation procedure, we recommend to test that your cache invalidation/load procedures are working as intended.

  • Fixed a bug where the cache-client would send to the server a PUT request instead of a LOAD request #182

V2.7.0

15 Jul 14:14

Choose a tag to compare

  • Changed messageID generation for client-server messages (see #174)

v2.6.0

21 Feb 18:25

Choose a tag to compare

What's Changed

  • #170 Cache server loose track of client known keys on concurrent fetch and invalidate

No breaking changes

v2.5.0

24 Jan 16:04

Choose a tag to compare

News:

  • Dependencies upgrade

No breaking changes

v2.4.0

23 Jun 09:37

Choose a tag to compare

News:

  • Support for ops/mem usage metrics

No breaking changes