OpenWGA 6.3 controls attachments and optimizes image sizes - new REST-API and Cluster Communication & Management Service
Join the DZone community and get the full member experience.Join For Free
the new version 6.3 of the java-based open source cms openwga boasts new automatisms in the treatment of file attachments and presentation of images on the website. in addition several apis for restful web services, support for high-resolution displays by the use of "client hints" and a new cluster communication framework based on hazelcast has been added.
smaller database - less space and shorter backup
openwga 6.3 stores identical file attachments only once into the database. this saves space on the server hard disk and shortens the daily backup process. "at first glance, one might think that hard drives are cheap today" said wolfgang schmidetzki, managing director of innovation gate. "but this is only true for desktops. disk space on servers is usually limited and is reluctant to be increased. an extension always requires a good argument and a lot of effort. with openwga 6.3 we usually can halve the size of the space occupied by the cms database". even the web author benefited from the new feature. since the attachments do not need to be copied when creating new page versions, it can be created much faster.
pictures load faster
even if authors add high-resolution images that would be suitable even for print, openwga 6.3 holds loading time of the webpage small. once an author uploads a new picture to a website, the cms automatically creates "image derivates" in several different sizes and stores them in the database. openwga then uses a web-optimized version with the ideal resolution for the position on the page where the image is added. if the author moves am image from a wide content column to a small teaser column, the system immediately uses a smaller version. all this is done completly transparent for the author.
integration of restful apis
new in openwga 6.3 is also a package for restful web services (data exchange is based on xml or json) with four different apis (cms api , hdbmodel api , query api and custom api).
"the scope for the rest api i see primarily where our cms must provide data for mobile apps. if you want to implement an app that presents products, the necessary data are already on the web server and can be accessed by the app online, instead of being newly maintained separately for the app. that way, the cms server becomes the central data hub for all other media" said schmidetzki.
cluster communication & management service
the new openwga 6.3 cluster management framework does not only support secure cluster communication and distributed task execution. it also comes with its own integrated session replication with optimized resource handling.
together with clustered dbms platforms like percona xtradb cluster openwga cms cluster can be used in distributed data center environments (wan/geo-clustering).
Opinions expressed by DZone contributors are their own.