Documentation:Slave server in action: Difference between revisions

Slave server in action

Revision as of 22:36, 16 June 2024

Write the content here to display this box

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.

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 18 days ago on 06/17/2024. What links here

Revision as of 15:46, 10 February 2024 (view source) Wikiadmin (talk \| contribs) (Automatically adding template at the end of the page.) ← Older edit		Revision as of 22:36, 16 June 2024 (view source) Wikiadmin (talk \| contribs) (Adding message template to the top of the page) Newer edit →
Line 1:		Line 1:
			{{message\|Write the content here to display this box}}
	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.