riscos and sockets

I’m busy writing a jabber client at the moment, however I have noticed that if there is data left to read and I write data, the socket seems screwed up.
Data is still sent by the server, however RISC OS seems to drop any further data that is sent to it.
I can still write data, but any data read never appears in RISC OS.
i.e. all further attempts to read from the socket end in select returning 0

Most strange, it’s like the socket inside RISC OS is a “simplex” one.
Not sure if this is a recent “feature” or it’s always been like this, or that all sockets work like this and I’m expecting it too but it doesn’t

I have worked around this by always ensuring the socket is fully “read” before writing – which isn’t a problem (and is probably what I should be doing anyway). But would appreciate comments.

If your coding for multiple sockets, it’s essential to ensure you don’t get your sockets entwined.
Seems my simplex issue was caused by re-entering wimppoll and losing the socket on one of the checks….damnit!