Timothy Flynn 64abc6101d LibWeb+WebWorker: Use IPC mechanics for structured serialization ... Our structured serialization implementation had its own bespoke encoder and decoder to serialize JS values. It also used a u32 buffer under the hood, which made using its structures a bit awkward. We had previously worked around its data structures in transferable streams, which nested transfers of MessagePort instances. We basically had to add hooks into the MessagePort to route to the correct transfer receiving steps, and we could not invoke the correct AOs directly as the spec dictates. We now use IPC mechanics to encode and decode data. This works because, although we are encoding JS values, we are only ultimately encoding primitive and basic AK types. The resulting data structures actually enforce that we implement transferable streams exactly as the spec is worded (I had planned to do that in a separate commit, but the fallout of this patch actually required that change).		2025-07-18 10:09:02 -04:00
..
WebWorkerClient.cpp	LibWeb: Fix typos - act II	2025-04-09 15:05:20 +01:00
WebWorkerClient.h	Everywhere: Make TransportSocket non-movable	2025-04-09 15:27:52 +02:00
WebWorkerClient.ipc
WebWorkerServer.ipc	LibWeb+WebWorker: Use IPC mechanics for structured serialization	2025-07-18 10:09:02 -04:00