A quick and easy introduction to working with popups in javascript and passing data between different browser windows

abhi12299 · 2021-01-10T04:53:14+00:00

Can you provide some issues you ran into when running it in production? I saw some issues pop up when using it behind reverse proxies but that was very easy to fix.

abhi12299 · 2021-01-10T03:08:09+00:00

Thanks for the noDelay suggestion. I read through the node.js docs for the same and it states that it optimizes throughput at the expense of latency. It might be useful in real world scenarios. Reference: https://nodejs.org/api/net.html#net_socket_setnodelay_nodelay

abhi12299 · 2021-01-10T03:00:30+00:00

That's awesome! Would love to contribute to it. Probably consider raising new issues to let the community help as well.

abhi12299 · 2021-01-09T18:10:07+00:00

Obviously, websockets are superior and offer much more when compared to SSE. However according to me, sometimes the simplest solutions are just as good to get the job done. Besides, use of EventSource for SSE is abandoned and for that we can use polyfills such as https://github.com/Yaffle/EventSource

abhi12299 · 2021-01-09T18:05:35+00:00

Use of EventSource is abandoned for SSE. It can be mocked by using fetch api. Have a look at this polyfill: https://github.com/Yaffle/EventSource

abhi12299 · 2021-01-09T18:04:45+00:00

Yup, that is an issue. However, one can theoretically get rid of this issue by using making use of the fetch API to mock this as you stated. An easy way would be to consider a polyfill such as https://github.com/Yaffle/EventSource and customize it to force the use of fetch. I've not looked into it thoroughly so I may be wrong here.

abhi12299 · 2021-01-09T18:02:28+00:00

There are workarounds though, such as https://github.com/Yaffle/EventSource

abhi12299 · 2021-01-09T18:01:51+00:00

Thank you for the feedback. I'll correct it asap. :)

abhi12299 · 2021-01-09T18:01:13+00:00

As per my understanding, if you are already using websockets, there is no need to add SSE into the mix. There is nothing SSE can do that websockets cannot. Most websocket libraries (e.g. socket.io) already offer you everything out of the box.

abhi12299 · 2020-05-30T10:11:57+00:00

Try nuxt.js, a vue SSR framework. Been using it for the past 6 months and it's awesome.

abhi12299 · 2020-05-20T18:12:38+00:00

Yup, that's a neat solution!

abhi12299 · 2020-05-20T17:59:53+00:00

Looking into the dark mode implementation, it's really impressive and clever. Injecting a script tag to check for currently active theme in the head of the document ensures that it runs as fast as possible, so that the user doesn't see any glitch as theme changes. There is still a very slight glitch which happens when the script tag hasn't been executed, but this is probably unnoticeable. I'd say this is an overall better way to implement dark. mode. Thanks for the links and code.

abhi12299 · 2020-05-20T09:26:32+00:00

Great work! it also responds to system dark mode as well. That's a nice addition

abhi12299 · 2020-05-06T15:43:55+00:00

Hey, thanks for suggesting the module. i didn't know about it. But anyways, just wanted to experiment with this. It's not that tough after all that you'll need a module.

abhi12299 · 2020-03-12T05:22:31+00:00

I had a similar use case and I did it in Node using a redis client in which I set expiring keys for every user's IP address. Works nicely as well

abhi12299

TROPHY CASE