MMM-NEWS problem

stuartiannaylor

@sean Look I am using many modules and hard refreshing with zero problems.
Tell me what your module is and what it is supposed to do under a hard refresh and what error it will cause.
I already know the answer none, but hey will test it and see.

Every module I install on config change auto restarts the server which takes seconds. The connection between browser and server is broken.
Browser waits for server to say hey port 8080 is ready then browser hard refreshes.
It takes 10 - 20 seconds 10 for server and the browser still holds the last screen then on ready hard refresh, browser dumps its cache and its the same as first time connection to the site.
Yes you can hard refresh and its vastly quicker than killing a browser for absolutely no apparent reason apart some misunderstanding of actual use.
Its vastly faster than killing and reloading the browser and its seemless without any horrid white screens oh awe snap or whatever it says.
Install my guide on a Pi and watch it do as I am trying to say.

https://github.com/StuartIanNaylor/MagicMirror-Install-Guide-Raspberry-0-to-3

A Former User

@stuartiannaylor
First I can’t understand why are you teaching me about usage. :D I’m not the who is trying any HARD or SOFT refreshing.

I believe you are using many modules without problem. But I’m also developing above 30+ MM modules for this community for some years. :D

I already know WHAT ERROR some of my modules might have when MM is refreshed. And know also it is just caused by its design. I’m saying just some modules could not be working due to its design when a user refreshes MM by force.

stuartiannaylor

@sean Just say what it is and which module and I will test it and prove either you or I are right.

Its that simple as every module I install when I click save on config.js I never need to kill my browser and have gone through 5 to 10 modules at least without trouble and without restart.
Just say which modules and lets test to see who is mistaken?

Browsers are stateless and if the server has been reset and the browser drops its cache its the same as running new.

A Former User

@stuartiannaylor
I think this is very meaningless argues.
Anyway, This thread is posted by @costascontis originally. He had a problem with MMM-News whenever he does screen refreshing with Ctrl+R. And as a creator of this module, I answered this module is not designed for that unexpected action. That’s all.
So, See that module and explain me anything what you want.

stuartiannaylor

@sean ctrl+r is a soft refresh not a hard refresh and it retains the cache.

Its only piontless because for some reason you will not simply state the modules you know have problems with hard refreshes.

Needs to be ctrl+F5 with chromium or whatever the shortcut key for hard refresh is.

A Former User

@stuartiannaylor
I’M NOT THE WHO HAS PROBLEM WITH REFRESHING. @costascontis is the one who ask this things. So you seems to be speaking to wrong person.

stuartiannaylor

@sean said in MMM-NEWS problem:

REFRESHING MM, not RESTARTING could make problems on many modules(including mines.). Regardless some modules would be not affected, but some would.

It depends on design of module structure. I do some tricks on DOM_OBJECTS_CREATED as a signal for ready of working. When MM is started and be ready for all DOM being prepared, that notification is emitted. Only one time emittance of that notification is expected during execution, not twice or more. But REFRESHING will break that agreement.

When MM Front is refreshed, MM modules would be restarted but some background-procedures (like node_helper.js or related background external scripts) are not killed or restarted properly. Because, many of them are not designed to be REFRESHED.
REFRESHING is some kind of interrupt from User. It couldn’t be predicted or postponed by condition. so, cannot be done killing or restarting process gracefully and safely.

So, It’s better not to REFRESH. RESTART MM instead.

I am replying to that which just isn’t true.
So when refreshing always do a hard refresh which on Chromium is ctrl+F5 pretty sure ctrl+r is the same as F5 and a soft refresh where it keeps the cache.

A Former User

@stuartiannaylor
THIS IS THE MODULE I’VE CREATED!! So I know what happens whenever @costascontis does Ctrl+R.

Anyway, this module will be newly getting the source to aggregate when it is refreshed (Hard or Normal whatever). And the reason is I’ve made so because I didn’t expect User doing refresh MM by manually. That is not related with any cache or any refresh mechanism at all. I JUST MADE THIS MODULE TO ACT SO BECAUSE I HAVEN’T EXPECTED SOMEONE REFRESH IT BY FORCE.

Back to the MMM-News,
Even whatever Hard refresh(Ctrl+F5) or Normal refresh(F5), This module will be accumulate the sources and show articles duplicately.(Because I made so). So I told @costascontis to RESTART instead REFRESH.

So now, What isn’t true as you said?

stuartiannaylor

@sean I have MMM-news by the side of me and do not have to restart the browser just the server,

A Former User

@stuartiannaylor Of course, RESTART is not also needed usually to normal users. My module is working as expected in commonway.
I don’t know why @costascontis needs REFRESH or RESTART, but he just said he has a problem on REFRESH so I explained him why module has a problem on refreshing(hard or normal whatever) and told him not to REFRESH my module. but if he want it anyway, RESTART instead. That’s all.