I’ve been fascinated by Silicon Graphics hardware for a very long time. Growing up, I had owned or at least had good access to a decent number of Silicon Graphics machines from the Indy up to the Octane series. I loved the industrial design of the hardware itself, as well as how capable and bulletproof they seemed.
Following on from yesterday’s post about reactive programming using Spring Reactive Web, I thought it would be interest to expand upon the example. In this post we’ll take a look at one of the cooler aspects of the new reactive model, result streaming.
Without going into too much backstory around reactive programming, the short explanation is that it is a technique for writing asynchronous, event driven, non-blocking applications.
I’m hoping to write a few posts about some of the techniques I’ve been playing around with. I’ve been really interested in keeping my services as functional as possible.
Retroactive continuity, or retcon for short, is a literary device in which established facts in a fictional work are adjusted, ignored, or contradicted by a subsequently published work which breaks continuity with the former.
Over the last decade or so I have posted quite a few things the various websites I have run. None of these websites are around any more, but the content sat in my archives waiting to be placed back on the internet. I figured this place was as good as any to upload my content to.
The writing quality is highly variable. The resolution of my photos from the era even worse.
Minor update: I think I’ve found some of my oldest content, dating back to the start of 2004.