Good, glad to hear it works. If you can avoid dealing with raw sockets and use a standard protocol for communication, that might allow you to write your network code at a nicer level of abstraction. What kind of network application are you trying to write?
In retrospect, perhaps that should have been the first question on this thread. Sorry I didn't ask earlier. For example, HTTP would be an example of a protocol whose language is in terms of requests and responses, rather than socket sends, receives, and flushes. ____________________ Racket Users list: http://lists.racket-lang.org/users
