eclipse-sailing-analytics/sailing-analytics
1
0
Fork 0
mirror of https://github.com/eclipse-sailing-analytics/sailing-analytics.git synced 2026-09-22 21:55:39 +00:00
Code Activity

bug5221: minor adjustments to release notes

Browse Source
This commit is contained in:
Axel Uhl
2020-09-22 11:03:56 +02:00
parent 6af7dbceaa
commit 847be8c0b5
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
java/com.sap.sailing.www/release_notes_admin.html
+5 -5
View File
@@ -25,12 +25,12 @@
<div class="innerContent">
<h2 class="articleSubheadline">September 2020</h2>
<ul class="bulletList">
<li>Due to loadbalancing request between master and replica all GET requests are routed to replicas. As API calls
going to /sailingserver/api/v1/tracking_devices/[deviceUUID] need to be answered by master, HTTP Post is required from now.
Please update existing applications. As support for GET will be removed in the future.
<li>Due to loadbalancing between master and replica all GET requests are routed to replicas. As API calls
going to /sailingserver/api/v1/tracking_devices/[deviceUUID] need to be answered by master, HTTP POST is required from now.
Please update existing applications. As support for GET will be removed in the near future.
</li>
<li>Master/replica loadbalancing introduced. GWT Async Services are now splitted between read and write operations.
Requests being a HTTP Post or having the HTTP header X-SAPSSE-Forward-Request-To set to master will go to the master instance.
<li>Master/replica loadbalancing introduced. GWT Async Services are now split between read and write operations.
Requests being an HTTP POST or having the HTTP header X-SAPSSE-Forward-Request-To set to master will go to the master instance.
</li>
<li>In the /competitor/live API end point, if a gap to leader turns "infinite" because a VMG
goes down to 0.0kts, the API will now output a <tt>null</tt> value for <tt>gapToLeader-s</tt>