That's why you usually use multi-tasking for communication software. ;-)
Anyway, server-side streams in BlitzMax are non-blocking and I never experienced that behaviour there. As for opening a client stream, that's a slightly different story. You usually -want- to know whether the called server is there, won't you?
Since we don't have multi-tasking in BlitzMax, you can put the communication layer in a second process and communicate with that. A lot of effort, and only you can know whether it's worth it.
Next option: Use you OS' socket API directly.
Ok, gotta go.
|