DB Image Cache

Stable Version 1.3.0 (OutSystems 11)
Published on 26 October 2018 by 
Created on 14 October 2018
Available in OutSystems versions:
OutSystems 11

Version 1.3.0

Stable
Current
Module
Published on 26 October 2018 by Rui Lopes
Requirements
Platform:
11.0.0.200
Database:
All
Stack:
All
What's new

In this version you will get:

  • Delete rule for DB image details has been changed allowing easier deletion of an image
  • Taking advantage of IIS 8.5 automatic ETag calculation (when available)
  • Fooling the browser to refresh an image after updating it via AJAX submit

The last correction is important specially when using a pop-up editor to update an image. Without it, the browser would assume the image is unchanged and the user would see the "old" image. Please upgrade to this version - the new ETag attribute is harmless and should not interfere with the timestamp-based behavior.

As usual, if you run into any problems, please let me know and I will try to correct them.

Still hoping you enjoy using this component!

Version 1.2.1

Stable
Module
Published on 21 October 2018 by Rui Lopes
Requirements
Platform:
11.0.0.200
Database:
All
Stack:
All
What's new

In this version you will get the following bug corrections:

  • The Last-Modified header now obeys RFC standard (the month attribute was incorrect)
  • The timestamp is now explicitly converted to GMT as required by the RFC standard
  • The body content of an unmodified image is now empty

The last correction listed is quite important so it is recomended you upgrade. Without it, there is no real performance improvement over the standard un-cached behavior.

Version 1.2.0

Stable
Module
Published on 21 October 2018 by Rui Lopes
Requirements
Platform:
11.0.0.200
Database:
All
Stack:
All
What's new

In this version you will get:

  • A separate entity for storing the images' details (following OutSystems' best practices)
  • The possibility to define private or public caching*

*when a resource has private caching, only the user's browser is allowed to cache it - intermediate proxies/gateways are not. If it has public cache, both the browser and intermediate network elements are allowed to cache it.

NOTE: This version's data model is not compatible with the previous versions' which means you will have to migrate your images' data.

Version 1.1.0

Stable
Module
Published on 15 October 2018 by Rui Lopes
Requirements
Platform:
11.0.0.200
Database:
All
Stack:
All
What's new

In this version you will get:

  • A new web block which retrieves the cached DB images via a REST service

If you want to keep your DB images behind a REST service, you will find this feature useful. Please note that, for sake of simplicity, the REST service has no authentication (even though it requires an SSL connection). Additionally, the provided web block (named DBCachedImageREST) requires you to expose it publicly. 

If you need extra security, please consider:

  • Investigating Service Studio's REST features (Authentication, Internal Access Only)
  • Providing your users the REST endpoint instead of exposing the web block publicly

Version 1.0.1

Stable
Module
Published on 15 October 2018 by Rui Lopes
Requirements
Platform:
11.0.0.200
Database:
All
Stack:
All
What's new

In this version you will get a bug correction:

  • The URL path referencing the cached image screen was hard-coded to Image.aspx which would not work on a JAVA stack. The hard-coded string has been replaced by the GetEntryURL() function which is stack-agnostic.

Version 1.0.0

Stable
Module
Published on 14 October 2018 by Rui Lopes
Requirements
Platform:
11.0.0.200
Database:
All
Stack:
All