I see big room for optimizations here.��

Look at very small unit of communication: delivering integer result (from [1+2] evaluation). Following object is responsible for this:

request := SeamlessDeliverResultRequest result: (SeamlessReturnValueResult with: 3) to: (SeamlessRequestContextReference id: 4 peerId: UUID new) .

stream := ByteArray new writeStream.

FLSerializer newDefault serialize: request on: stream.

bytes := stream contents.

bytes size. "==> 412"

(ObjectTraveler on: request ) countReferences ��"==>10"

��

Last line shows that only 10 objects consists full object graph of request. And Fuel serialization takes for it 412 bytes.

It definitely could be improved with specialized serialization protocol. Also it could allow object traversal once which will lead to another performance improvements.