hyperstack-org / hyperstack-org/hyperstack

Hyperstack.on_server? can do much better please

Aperta
#345 1 commento 1 reazione 0 assegnatari Vedi su GitHub
enhancement needs doc
Lingua principale
JavaScript
Stelle
538
Fork
41
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

Currently `Hyperstack.on_server?` returns false if you not on the rails server (i.e. on the console or on in a sidekiq worker).

The system uses this to decide if it needs to forward any broadcasts to the server from, under the assumption that if you are not on the server you do not have access to the broadcast mechanism.

This assumption is pretty weak. The following are known cases where it doesn't matter:

you are using simple_poller (in this case you are going to shove the message into a queue, and wait for the next poll)

you are using action_cable NOT in async mode. (i.e. the connection data is stored in a database, not in the servers memory)

Not tested is pusher, and actually not tested (but I'm sure it would work is action_cable and redis)

Soooo...

This method should be called: forward_messages_to_server?
and should check to see if we have to forward it, by a combination of checking configuration and/or checking actual behavior.

Why should I care?

Because if you are using a lot of outside processes to do stuff, then you are adding unneeded overhead forwarding this stuff to the server.

The current work around is very simple: Just add this line to the hyperstack initializer

`def Hyperstack.on_server?; true; end`

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.