Using the online scriptures and comments

This is really a powerful tool for scripture study. Is there some limit to how much you can post? I have to constantly log out and in in order to post my comments on scripture. Why is that? Is this tool supposed to be used less?

If this worked right, I would use it all the time for scripture study. Why is it so unreliable? - Frustrating that the tool is so poorly set up. Its a great concept, but it just does not work. Any suggestions on perhaps a better solution, but what better solution could there be than to keep your scripture study notes on the Church website? Please, if there is some secret to getting this to be reliable, please share, As it is, I am about to abandon it and try something else.

FYI: I work from home and my bandwidth is as good and reliable as it gets.

1: Is there a limit to what I can post?
2: Is anyone else having this issue
3: Is the church planning on fixing this anytime soon?

A scripture study school that only allows minimal input. = Not very useful.

Most likely what you're running into is that there's a time out. If you don't change or refresh the page in a certain period of time, you will automatically be logged out. The server has no way of knowing you are still looking at the page. It's the same as if you closed the page and walked away. All it knows is you haven't made any requests or changes in a certain length of time.

russellhltn wrote:Most likely what you're running into is that there's a time out. If you don't change or refresh the page in a certain period of time, you will automatically be logged out. The server has no way of knowing you are still looking at the page. It's the same as if you closed the page and walked away. All it knows is you haven't made any requests or changes in a certain length of time.

If that's the problem, one solution could be that you get prompted with some kind of "are you still there" message before you get logged out. I run into that on some web sites (especially banks, since I think they quickly log you out for inactivity for security reasons). It's helpful, as sometimes you're just taking a while to read things.

mevans wrote:If that's the problem, one solution could be that you get prompted with some kind of "are you still there" message before you get logged out.

That may depend on the details of the connection with the server. It may take more overhead for the server to have the kind of connection where it can initiate such an action.

russellhltn wrote:

mevans wrote:If that's the problem, one solution could be that you get prompted with some kind of "are you still there" message before you get logged out.

That may depend on the details of the connection with the server. It may take more overhead for the server to have the kind of connection where it can initiate such an action.

There are multiple ways to implement such a feature. The server doesn't necessarily have to initiate the action; there could be a JavaScript timer on the page that gets reset with server interactions. When it reaches the determined count due to lack of action, it prompts you with a countdown. If you don't respond, it connects to the server to do a logout. If you set the timer to be less time than the connection persistence on the server, then you don't have to worry about the server logging you out before the web page logs you out. Of course, it all comes down to the business requirements in the end.