Rank: Advanced Member
Groups: Registered
Joined: 6/23/2015(UTC) Posts: 59  Thanks: 5 times
|
I have saved a few small images below $PERSISTENT. When I'm starting the workflow on a mobile device those images are transferred to MT server during the starting phase. This was not intended, what parameter to set to avoid this?
Thanks
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 6/23/2015(UTC) Posts: 59 Thanks: 5 times
|
I found out that this happens when a "Load from HTTP" action is triggered (in this case a trivial GET request). My workflow starts with an HTTP request, that's why I need to wait a long time before the first page will be visible.
Transferred data look like a XML export of $PERSISTENT.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 6/23/2015(UTC) Posts: 59 Thanks: 5 times
|
Thanks, already sent to support.
|
|
|
|
|
|
Rank: Administration
Groups: Registered, Administrators
Joined: 7/21/2014(UTC)
Posts: 498
Was thanked: 88 time(s) in 88 post(s)
|
This is correct, because MobileTogether is able to execute parts of actions on both Server and Client, and for this it has to have access to all data.
We have already a setting "Keep data on server" which tells MobileTogether to never transfer data from Server to Client. A setting for the opposite is on our ToDo.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 6/23/2015(UTC) Posts: 59 Thanks: 5 times
|
Are you sure it's correct that persistent data are being transferred to server, especially $PERSISTENT datasource? This can kill performance totally. Quote:Manual - Persistent Data Storgae on Clients:
For user-entered data and data that doesn’t change too frequently, you can choose to store data persistently on each client device. This reduces the amount of data being transferred between the server and client, and so increases performance speed. It also provides a performance boost because it reduces the round-trip time between server and client—even between different sessions of the same user that end up being hours apart. That’s because the data is saved persistently on the client device.
|
|
|
|
|
|
Rank: Administration
Groups: Registered, Administrators
Joined: 7/21/2014(UTC)
Posts: 498
Was thanked: 88 time(s) in 88 post(s)
|
A $PERSISTENT only means that it remains saved on clients between the runs allowing user to continue his work where he started.
Now imagine, to enable this continued feel, you want to load database data or HTTP file or choose a completely different initialization depending on what is saved in $PERSISTENT - it must be transferred to Server. As I said, in future it will be also possible to inform MobileTogether that you will never ever want to have such dependency and therefore data must not be transferred to Server - in this case any attempt to retrieve data from such trees on server will trigger an error. But in most cases the current logic is perfectly correct.
P.S. you are right - we need to be more clear in documentation.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 6/23/2015(UTC) Posts: 59 Thanks: 5 times
|
feature request: "48758 - Ability to 'keep data on client'"
|
|
|
|
|
|
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
