Currently it's not possible to pass Stream objects through methods of remoteable interface. This would be really useful when trying to transport vast amounts of data than merely sending a 1Gb blob via a byte[] parameter:
- Sending a huge blob blocks every other RPC until the blob has been sent (Okay this is a current implementation issue, but I'm not comfortable writing packet disassembly and assembly on top of TCP, seems like a waste of my time)
- If there's a problem during transfer, then the entire thing must be sent again, if Streams were used then it'd be easier to resume where one left of
- Stream offers Read/Write-Async methods which fit nicely into SharpRemote's philosophy
Goals:
- Write tests to show usage of Streams with remoteable interfaces
- Create transport interface, proxy Stream implementation and Stream servant
- Adapt serializer implementations to create proxy/adapter when encountering Stream objects
Currently it's not possible to pass Stream objects through methods of remoteable interface. This would be really useful when trying to transport vast amounts of data than merely sending a 1Gb blob via a byte[] parameter:
Goals: