Slave server in action
No edit summary
(Automatically adding template at the end of the page.)
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
After setting up a slave server you can do simple tests to verify the function.
After setting up a slave server, you can do simple tests to verify the function.


In this a animated GIF I have two appliactions running a UI that has PeriodicAction that does a simple update of an attribute - and then a refresh and a save.
In this animated GIF, I have two applications running a UI that has PeriodicAction that does a simple update of an attribute - then a refresh and a save.


I also run the prototyper as a 3:th app against the Slave server.
I also run the prototyper as a 3:th app against the Slave server.
[[File:2018-06-06 23h51 30.gif|none|thumb|844x844px]]
[[File:2018-06-06 23h51 30.gif|none|thumb|844x844px]]
Notice that the lower of the 3 is a bit choppier when getting data refresh for the first two rows that are updated in the Master db.
Notice that the lower of the 3 is a bit choppier when getting data refresh because the first two rows are updated in the Master DB.


This because the transport via the MDrivenServerSynk.
This is because of the transport via the MDrivenServerSynk.  


This is the expected behavior of a Slave server.
This is the expected behavior of a Slave server.
Line 20: Line 20:
  selfVM.Refresh;  
  selfVM.Refresh;  
  selfVM.Save
  selfVM.Save
[[Category:MDriven Server]]
[[Category:MDriven Server]]
{{Edited|July|12|2024}}

Latest revision as of 15:46, 10 February 2024

After setting up a slave server, you can do simple tests to verify the function.

In this animated GIF, I have two applications running a UI that has PeriodicAction that does a simple update of an attribute - then a refresh and a save.

I also run the prototyper as a 3:th app against the Slave server.

2018-06-06 23h51 30.gif

Notice that the lower of the 3 is a bit choppier when getting data refresh because the first two rows are updated in the Master DB.

This is because of the transport via the MDrivenServerSynk.

This is the expected behavior of a Slave server.

The PeriodicAction looks like this:

vCurrent_Details.Company.Name:=vCurrent_Details.Company.Name+'x'; 
if vCurrent_Details.Company.Name->length>10 then  
  vCurrent_Details.Company.Name:='C' 
else  
  '' 
endif; 
selfVM.Refresh; 
selfVM.Save
This page was edited 98 days ago on 02/10/2024. What links here