Unsequenced socket bug fix

| 0 Comments

I've just fixed a bug in the latest version of The Server Framework (v5.1 - if you dont have docs and a version number then you're < 5).

The probelm was that I was being fractionally over-zealous in making things easy for the user... CStreamSocket has a RequestWrite() method that takes a BYTE * and a length. Originally this used to fail if the length was more than the size of a buffer. Then I fixed the problem so that it split the write over multiple buffers. Unfortunately this is the wrong thing to do if write sequencing isn't enabled. So now if you want that functionality you have to use CSequencedStreamSocket, that is create sockets from an instance of CSequencedStreamSocketAllocator rather than from CStreamSocketAllocator.

Leave a comment