Umm, wish I had more time to investigate.
Two days ago I set up Wireshark to look at the network traffic between my Browser (Ubuntu Firefox, both up-to-date) and noted that the initial page load appeared ro be cached locally, ie read from a copy stored on my computer not retrieved from the server. May be a false conclusion because Wireshark takes careful setting up. After logging in, I got server updates.
Just tried again and it looks as if a major change has been made at the server end. Two days ago, my Browser and the server communicated in standard HTTPS (web pages) and TLs (encryption set-up and refresh) both TCP. The network connection is IPv6. (old network used IPv4).
Different today: still IPv6, but the protocol has changed to QUIC not TCP. QUIC is faster than TCP, but not everything supports it. It means behind the scenes the new forum is doing a more complicated job than the old. Nothing to do with look and feel, but it’s switching how it connects to individuals/ Presumably anyone with an ancient Windows-7 box gets an old-school IPv4 /’ TCP connection, whilst those with up to date hardware and software get a different service. Both are risky: ancient because out-of-date software gradually becomes obsolete, whilst brand-new technology tends to be bleeding-edge – buggy!!!
Therefore individual experience could vary significantly. Results depend on our hardware, the software it is running, how it is configured, our router, what our ISP supports, and a similar stack of dependencies at the host end, plus the performance tuning needs of a largish database and account management system. The host end is more likely to be up-to-date.
Mortons were forced go live before the forum was fully debugged and are now struggling with a difficult IT problem, which is debugging a live site. In development mode, there are no external host, network or client problems: bugs can only be due to the forum software, and the developer can experiment with solutions freely to find a fix. Now the developer has to identify where in a very complex environment the bug really is, and there’s a high risk of causing new problems by changing the configuration experimentally. Nasty, and applying fixes takes much longer.
From user end, there are two false views:
- Those who experience the worst think the whole thing is beyond redemption. They’re wrong.
- Possible for occasional users not to notice there is anything odd going on. This is wrong too.
- The truth is the forum is poorly – not delivering as intended, and fixing it has proved difficult. A serious engineering problem, and a hard slow slog to get it ‘just so’. No doubt some annoying cosmetic problems haven’t been touched yet because the developer is embroiled in difficult stuff.
At the moment, I think suspect two or more bugs are interacting:: initial login, cache(s) not being refreshed causing old data to stick in the system, posts appearing in threads, or disappearing, and sluggish performance. It’s possible all are cache related. Simply put, if data hasn’t changed since the last request, use a local copy, i.e a cache. But this only works if the cache refreshes correctly when the source data is changed. Quite complicated to configure, and it can go wrong, causing peculiar misbehaviours!
Out of time, have to hit the road – hope this makes sense.
Dave