MMM-NEWS problem

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.

stuartiannaylor

@sean said in MMM-NEWS problem:

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 m

I will just quote you once more and say that its not true, but hey.

You can not make a module bridge the stateless gap of browser and server.
The server is incredibly light and its the server that needs to restart the browser can just do a hard refresh and doesn’t need to restart.
It all depends on the way you have installed if your using electron because its in the same process as the server it forces both.
If you install with chromium then you don’t have to restart the browser.

A Former User

@stuartiannaylor
I DON’T NEED ANY RESTARTING OR REFRESHING FOR MY MM !! IT WORKS WELL ALWAYS EVEN ON ELECTRON OR CHROMIUM.
This situation is something like speaking to the wall…

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 …

the reason is I’ve made so, have you missed this? I’ve made this module to act like that.

So, Test my MMM-News with Hard refreshing or Normal refreshing. It will aggregate duplicated articles because I’ve made so. People can call it a bug or an issue or unexpected misbehavior whatever. But I made it like that! because usually REFRESH by user is not needed for MM. It is not designed for being REFRESHED.
Why you said this is not the true?

stuartiannaylor

Sean I have it by the side of me and because I restart the server without need to restart the browser there is no aggregated duplicated articles.
It doesn’t happen and irrespective of who or what you are I have it by the side of me installed it without restart and others after with no duplicates as how could there be when the server has been restarted and the only remnants in cache have been dropped by a hard refresh.

Pfff enough of this as the universe is flat Sean, flat! Do you hear me!
Its a bug for those who have installed electron but if you use Chromium and do it my way its doesn’t matter.

A Former User

@stuartiannaylor
Of course, restarting wouldn’t make duplicated articles.
This module works nicely unless user REFRESHES it by manual.

I’m saying just my module is not designed for being refreshed. because REFRESHING will make my module to send socketNotification "START" to node_helper.js for scanning news source again unexpectedly. It is not related with which front browser is used, or which cache remains or not, or which mechanism is used for refreshing.

Its a bug for those who have installed electron but if you use Chromium and do it my way its doesn’t matter.

I don’t care how ppl use my module. So you can call it a bug. But usually people is using Electron as MM’s front and, usually there be no need to REFRESH MM by manual. A bug or not, I don’t care.

stuartiannaylor

Its not your module shaun but bugs elsewhere with freezing modules has some refreshing and then that cascades down to yours.

All I am saying is if you want a fix don’t go the electron way as because its part of the server it gets restarted with the server so you end up due to other modules periodically restarting with the effect that gives of flashing screens and desktop views.
What I am saying is that actually if you use chromium you don’t need to restart the heavy browser as you can keep that in view. You can restart the server and then do a hard refresh and because you start from a restart on the “Ready to go! Please point your browser to:8080” it can have no effect on any module.

That is it Sean and we shall not say argument but its you telling me that isn’t true when it is and I have your module MMM-news on a screen doing the above without restart and no duplication.
Its how I set it up because it has puzzled the hell out of me why with stateless browser / server technology you have lumped them into one?
As a roadmap you prob need to separate client / server or more users like this one will realise it works better when using chromium and not electron even though its only due to the way electron has been implemented.

I think your MMM-News module is the business and a large part of the way I did my setup was to make it work seamlessly with any module without needing browser restarts and it does that perfectly.
PS any chance when you bring the iframe of the full article up in an Iframe that you can enable and activate the DOM distiller so its in ‘Reader mode’?