GM PV Notroids, my recent travels are at an end, the resulting accumulated backlog has been eroded, and I rode 30 miles yesterday on my Terra Trike. I've got a plan for the next modifications to more-speech.

The main problem is that I treat the relay websockets in unison rather than as independent devices. I open them all at once, and wait for them all to be open. When I send I send to all at the same time. This has to end.

So my next more-speech project is to create asyncronous processes for each websocket so that I can start sending as the websockets open, and I can queue up messages to those websockets that open later, or close down and then reopen.

This shouldn't be too hard because the input side of the websockets is already asynchronous. Right now I'm debating whether I should use clojure channels, or agents as the message queuing mechanism. I'm leaning towards agents.

Reply to this note

Please Login to reply.

Discussion

This is one of the things I love about my favorite language, C#. The managed thread pool makes optimizing things like this so easy.

Sounds like clojure has good support for parallelism too. We’re spoiled.

You haven't lived until you've written asyncronous code in PDP-8 Assembler.

I think I’m good. 🤣

Assembly is something I haven’t gotten too, and now things move so fast, I wonder if I will ever get time to.

Learning VHDL is something work may grant me the opportunity to try though.

If you'd like to spend a pleasant afternoon fiddling around with a PDP-8 I suggest looking into:

https://github.com/unclebob/pdp8EmulatorIpad

Sounds dope! I wanna get to this level of understanding about web dev.