Closed warpok closed 5 years ago
I do not yet understand what this is about.
If the "Cloud program would often not be able to show the Resources", how does the frequency of Send/Receive on the client relate to this?
The Internet connection was fast enough to give us verse changes in Cloud mode, but not fast enough to give us Workspaces with Resources.
On Fri, Apr 12, 2019, 10:09 AM Teus Benschop notifications@github.com wrote:
I do not yet understand what this is about.
If the "Cloud program would often not be able to show the Resources", how does the frequency of Send/Receive on the client relate to this?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bibledit/cloud/issues/262#issuecomment-482610518, or mute the thread https://github.com/notifications/unsubscribe-auth/AEckJcCqr18MOwESaO4RX8bhYhhohxs3ks5vgKGugaJpZM4csTsR .
So won't the solution be a faster internet connection, rather than a faster send/receive frequency? I am asking because you have a good reason for this issue, but I don't understand it yet.
The cell phone connection at our hotel varied in quality and speed for the different participants. Some tablets were tethered to phones. Other tablets had their own SIM cards and connections. If people were looking at the Translate > Verse editor, or the Basic Mode Translation page (not viewing resources), the cell phone connection was good enough for verses to be updated rather quickly, sometimes within 10 seconds. Other times it took 4-5 minutes and we might be on the next verse by the time some screens were updated. But that was still quick enough. People got used to the small lags and enjoyed working like this.
But the slowness of such a connection discouraged the translation team members from using the Resources in the cloud. Some of the team remembered to multitask so that they could use the Client app for viewing resources. We have over 24 resources, so the Client app with the resources pre-installed was the only way to get Resources in a quick manner. But this means that the user would have the extra steps of changing apps and then changing that 2nd app to the right verse. In a checking session like we were having, the team members really needed to see the Biblehub Interlinear frequently, and that is not a quick resource to have appear on a slower cell connection.
So if there was a setting to get new changes to the text in the Client program every 20 seconds, that would be frequent enough that the translation team members could use a workspace viewing both Resources and the Bible being translated on the same screen. The preinstalled resources would appear quickly. The team members wouldn't have to do the mental gymnastics of keeping track as to whether they were viewing the Client or the Cloud.
The 20-second setting would mean that potentially 6-8 devices would be continually doing a Send/Receive one after another every 2-3 seconds. Can the Server handle more than one update request at the same time? If one of the machines takes three minutes to get the updated text of a verse, does that mean that all the other machines have to wait 3 minutes before the next one in the queue can start? Can the Server can keep track of 3-4 connections simultaneously getting the same text? While the Server is doing that, could it also simultaneously receive a new change to the same verse? If the server could keep track of all that, then I would think that the 20 second setting would help teams of people in situations like ours. But if there can only be one connection at a time and assuming a data connection like we had, then the updates to 6-8 Client apps might still take 5 minutes. (In other words, not that much different than the default 5 minute setting.) So it could be that a 20-second setting would not help that much, depending on how the server works. Thanks for considering this.
I now understand the point of this issue. Thank you for explaining it in detail.
The server can handle multiple simultaneous connections. it will use threads for each connection. It will also be able to receive an updated verse at the same time.
So yes, the setting to send and receive every 20 seconds will help in a situation like yours.
I guess it's enough to send and receive Bible data only at that higher frequency?
Phil Fields
USA: 479-524-7005
Indonesia and Whatsapp: +6285 770 333 734
303 Ryan Ct., Siloam Springs, AR 72761
Pada tanggal Sab, 13 Apr 2019 pukul 08.37 Teus Benschop < notifications@github.com> menulis:
I now understand the point of this issue. Thank you for explaining it in detail.
The server can handle multiple simultaneous connections. it will use threads for each connection. It will also be able to receive an updated verse at the same time.
So yes, the setting to send and receive every 20 seconds will help in a situation like yours.
I guess it's enough to send and receive Bible data only at that higher frequency?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bibledit/cloud/issues/262#issuecomment-482809988, or mute the thread https://github.com/notifications/unsubscribe-auth/AEckJUbXKjaXVnqLK75HxU6zdXSXF5MNks5vgd2xgaJpZM4csTsR .
The good news is that the Android app and the Linux app both have been updated to be able to send and receive Bibles every twenty seconds. Good luck with that, and many happy translation team meetings!
In our recent checking sessions where we mainly used Bibledit Cloud, it would actually been helpful if we had a faster setting for Send/Receive in the Client program. The Cloud program would often not be able to show the Resources. It would help a lot if we could add a setting to do a Send/Receive every 22 seconds or so.
This would make it so that in a checking or other group situation, the Client users could see the resources and get updates reasonably quickly.