T
Tim Kuehn
Guest
Laura - I'd note that 13 years ago I spent ~2 months sorting through the socket docs to get a communications protocol working under 9.1, and while I was able to get something working and in production, it had data-loss issues at higher throughput that I couldn't resolve. Even today it seems there've been details I've missed - like when I'm in the READ-RESPONSE routine that SELF points to an endpoint socket object and not the server socket object. Was it my fault for failing to "get" that rather critical piece of information after 2 months of work? Or PSC doc's for failing to make it completely clear that an operational system had both a server and an endpoint socket? Had "socket object" been termed a "socket endpoint object" and the statement edited accordingly - it is via the socket endpoint object that clients and servers communicate The difference / distinction between the two would've been a lot clearer. Re: the data loss issue - I later learned that I needed to set hserversocket:SENSITIVE to FALSE in the READ-RESPONSE code...something I can't recall ever seeing in the docs. Also, back when I was first wrestling with this there wasn't even any demo code around to look at - the community had to figure all this out for themselves.
Continue reading...
Continue reading...