Re: Trouble w/sockets

[mark . d . witmer]

address@hidden writes:

> But calls to readv() after I do the select + usleep loop you suggest
> here just give me garbage data. (read-char) gets #<eof>.
>

Oh, and the return value (bytes read) from readv() is zero, so the
garbage data is just stuff in an unitialized bytevector. Looks like the
socket is still getting closed early.

>
> Thanks to everyone for their help. I feel like I'm close to figuing this
> out, but I probably need to take a break from this for a
> while. Hopefully I'll get this working at some point in the relatively
> near future!

Ok, now I'm taking a (multi-day, hopefully) break... thanks all.

-- 
Mark Witmer