TOPIC:

My problem is I click on a link to the club's agenda but the login page always prevents me from getting there. After logging in I still have to click on the link. Originally I was going to suggest increasing the cookie expiration so I don't have to log in as much, which is still an option. But even better would be to change the login so the user is sent to the originally requested page after logging in.

Well, as this is a single server system used by over 11,000 clubs/districts worldwide, there are a number of strategies employed to keep the system performing reasonably well... Expiring cookies to limit the amount of HTML transferred from the server is one of those strategies.(logged in results in more HTML sent to your computer)

I realize it is a bit of a pain, so in the future, I will likely be moving many of the dialogs to a "fetch as needed" approach to limit the amount of HTML sent on each refresh. This would allow me to do things like extend the cookie expiration, but at the expense of having more waiting/spinning and lags while dialog HTML and scripts are fetched from the server for features.

Essentially, there is no free lunch for performance. I get the general impression that it is probably better to fetch the code from the server for features as they are requested to be used rather than sending it at once in each refresh, so that this the direction I want to head in moving forward.

On the forwarding to requested page after logging in... yeah noted. I have had that in the back of my mind also. Patience please...

[retracted]

[retracted]

Ok, you think you know how the system works... you do *not*. I was *not* talking about the size of cookies.

I am not going to litigate or justify my design decisions here.

Sorry, I misread the "Expiring cookies to limit the amount of HTML transferred from the server is one of those strategies." I think my brain stopped there because if I had read the next part "(logged in results in more HTML sent to your computer)" more carefully I would've realized you weren't talking about the cookie size.

So, I was thinking about this on the way home and this is in no way dictating how you should run your site or how your system works. This is just a suggestion from a user to make *my* experience better...

If I come to the site without being authenticated then the server has to send me first the unauthenticated page. Then after I log in I am sent to the authenticated homepage. And finally I request the original page and am sent that. For this one use case only it seems that if I was already authenticated then I would just be served the one page instead of 3.

Again, I am just making an observation so don't get all pissed.

Well, the tone of your posts seemed rather antagonistic, particularly since you went to the trouble of making two successive posts. There are plenty of users that make observations and point out improvements... it does not normally bother me and I am very happy to read them--many of our best feature adds have come from our users. However, I felt I had gone the extra mile to explain why things the way the are, and yet you still chose to be antagonistic.

I could have just ignored your initial post to avoid the risk that you may not like my response, but I do not think that ignoring people is necessarily better than giving them a response they may not like. I felt you deserved an honest response, and that is why I took the time to try and explain why things are the way they are. (Normally, I would only post a few sentences.)

Lesson learned, though, aakoch.

support.toastmastersclubs.org/doc/item/terms-of-use-agreement

Yes, I was too antagonistic. I apologize for my tone. My understanding of the situation was incorrect and colored my response.

I'm sorry.