With Temporal, your activity logic still needs to ensure idempotency e.g. by checking if an event id / idempotency key exists in a table. It's still at-least-once delivery. Temporal does make it easy to mint an idempotency key by concatenating workflow run id and activity id, if you don't have a one provided client-side.
Yep, explorer.exe has always started up in the background. Pure speculation here, but this change likely involves preloading the UI surfaces and supporting bits such as disk free space, network share status, thumbnails etc.
Explorer.exe is not file explorer, it is the Windows UI system. It’s harder to see on modern Windows versions (since Windows will reload it automatically), but if you go into Win98 and kill the process, you’ll see your taskbar, desktop icons, right click menu, etc disappear.
File explorer is a part of that process, but consists of additional dynamic libraries and COM components that are loaded on-demand.
Old desktop replacements (like Litestep) specifically modified Windows to block explorer from loading the desktop to replace it (though, would still spawn it for file explorer).
Did you even read the blog post? It's almost a direct quote
> We’re exploring preloading File Explorer in the background to help improve File Explorer launch performance. This shouldn’t be visible to you, outside of File Explorer hopefully launching faster when you need to use it.
This bears the question of how does an exchange efficiently detect, log and take action against these kinds of behaviours without increasing its own latency too much and (perhaps?) affecting the market?
Does it even matter if a centralised exchange increases its own latency when all market participants have to go through it? I can only think of the case when a security is listed on multiple exchanges, where the latency could mean a small arbitrage opportunity.
Exchanges rarely care about their absolute latency. The latency race is for the best place in the order entry queue. As soon as the order is queued for sequential processing by the risk checker or the matching engine, the race is over. I've seen places where you needed sub-microsecond tick-to-order latency to win the race for the front of the queue, but the actual risk check and matching took tens of milliseconds.
They do care about throughput and providing fair conditions to all of the participants, though. On busiest derivatives exchanges this means resorting to FPGAs for initial checks.
Then, every message send to the exchange is clearly traceable. In some cases participants have dedicated physical lines. When the exchange sees increased rate of malformed packets from a single line or from a certain participant, they just cut it off and call the contact person from the participant (trader/broker) side to demand explanation.
Most exchanges have switched to order gateways that are either fpga or asic based.
Also every packet you send to an exchange is trivially attributed. They just kick you off if your shenanigans cause a problem. And then they tell all the other exchanges about you.
Off-topic for this thread but if you can get the ball to ping-pong horizontally while both players are at the top edge then you can stay alive indefinitely - the opponent doesn't seem to move downwards out of this position.
PDFs are ok but I prefer the SingleFile extension which has the benefit of not introducing page breaks which often split images in two. It also preserves the original source and assets in case one ever needs to extract them.
