cover.jpg

 | 
5 min read

Often there is the requirement to push data updates from the server to the client-side. Imagine a chat app showing incoming messages in the client’s browser. New messages should get displayed automatically without polling, the user shouldn’t need to trigger some action to fetch new messages. In general UI push updates (https://vaadin.com/docs/v15/flow/advanced/tutorial-push-access.html) are pretty easy to implement with Vaadin by default, but there are some special cases we have to deal with.

In this article I want to show you a way to achieve asynchronous UI updates with Vaadin without data flooding or overloading the server to client connection when many concurrent push requests arrive. In addition, if you use Spring Security with Vaadin, we probably want to have access to the user’s security context to authorize push updates before they get dispatched to the client’s browser.

cover.jpg

 | 
1 min read

Recently I had to transform ViennaGIS Gauß-Krüger M 34 MGI Austria GK East coordinates to Google WGS84 using EPSG code 31256. The use case was to show pins on Google Maps or Leaflet of ViennaGIS provided objects and locations.

cover.jpg

 | 
1 min read

An alternative to the built-in Jira Agile Board. Displays all relevant Sprint data. Currently tested with Jira Cloud only. It’s a convenient pure digital Agile board if your team is not co-located, it can be used as an alternative to physical Possy boards.

cover.jpg

 | 
4 min read

Tired of writing tasks by hand? - In this article I want to introduce Possy, a tool to print cards with POS printers for physical task boards with data provided by issue tracking systems, e.g. Atlassian Jira.