Client-side reloading logic for hot variables

[bakape]

Rerender #banner_info, #schedule, etc.

[ghost]

The schedule shouldn't exist currently, and AFAIK everything updates just fine via websockets.
Close?

[bakape]

Configs only update on page reload.

…

On 6 September 2018 at 07:20, チルノ ***@***.***> wrote: The schedule shouldn't exist currently, and AFAIK everything updates just fine via websockets. Close? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#268 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHfPsHT6XdnspZIgeMfPMytXlJK85zeBks5uYKKOgaJpZM4F0Ift> .

[ghost]

I see, I'll add this to my TODO.
Unless you feel like getting to this soon for some reason.

[bakape]

Not soon. Work, then some bigger meguca changes.

…

On 6 September 2018 at 08:54, チルノ ***@***.***> wrote: I see, I'll add this to my TODO. Unless you feel like getting to this soon for some reason. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#268 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHfPsB2JGNuddgKDFL3GJ-ZP0vWA4mx5ks5uYLiEgaJpZM4F0Ift> .

[ghost]

@bakape Can I assume all these variables are in state.ts?
Anywhere else I may need to look?

[bakape]

The only 2 we need to sync are global configs and (maybe) board configs. Both are in state.ts.

…

On 8 September 2018 at 09:14, チルノ ***@***.***> wrote: @bakape <https://github.com/bakape> Can I assume all these variables are in state.ts? Anywhere else I may need to look? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#268 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHfPsDwB6PL2KN3Wo5VE_6M82YljN950ks5uY2BRgaJpZM4F0Ift> .

[ghost]

Syncing board configs might be a good idea due to red/blue text and pyu.

[bakape]

This was actually done previously in v2 and v3. 1) Write a hash of configs into the HTML templates with the config JSON. 2) Client sends this hash on connection. a) On mismatch server sends new config and hash. 3) On config update (see db/config.go) server resends new configs and hashes to all clients.

…

On 8 September 2018 at 22:46, チルノ ***@***.***> wrote: Syncing board configs might be a good idea due to red/blue text and pyu. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#268 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHfPsJ5zXL0kU6_ByRfn75vsmn4cWkTsks5uZB6HgaJpZM4F0Ift> .

[ghost]

Sending the whole config seems like overkill, perhaps we should only send the parts we know need/can be updated in the client on a live basis.

[bakape]

It's not much bigger than a big post payload-wise.

[ghost]

What would the frequency of these updates be?

[bakape]

Whenever configs are change.

…

On Sun, 5 May 2019, 20:20 チルノ, ***@***.***> wrote: What would the frequency of these updates be? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#268 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB347ME7G4G46WBOUM6BHCDPT4JL7ANCNFSM4BOQQ7WQ> .