[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Mon Nov 27 23:00:44 1995 
Subject:Re: reporting pop bugs (and pvars) 
From:A . Sloman 
Volume-ID:951128.09 

> > What a shambles!
>
> Never mind. Perhaps it's something to do with writing messages at 03:15
> on a Sunday morning.

Yes, and worrying about all the hassles of teaching - I have four and a
half courses this term, as a result of an administrative accident and
every little irritation like having to re-write all my teaching
documentation for no good reason makes me lose my cool...

Sorry about that.

(At least I'll be moving to the pure research role I came here for,
shortly.)

There are some good things in V15, especially the sockets package.
Speaking of which... I've converted my lib ved_gn (nntp news reader) to
use
	sys_socket_to_service(nntp_host_spec, "line");

This creates a connected socket which works like a charm with sysread
and syswrite, and noticeably faster than my previous trick of using
run_unix_program to invoke telnet. However, as someone who knows nothing
about sockets, I am puzzled by the fact that REF SOCKETS states:

For most purposes, sysread and  syswrite are sufficient for reading  and
writing sockets. However, these cannot be used

      o For out-of-band data on stream sockets.

and I have not been able to find out whether I need to take account of
that or not, since I can't find out what it means.

I experimented with sys_socket_recv instead of sysread, but it produced
different behaviour: the strings returned seemed to be different from
those produced by sysread, and consequently ved_gn stopped working. Does
anyone have a simple explanation of the conditions under which one
should use sys_socket_recv and sys_socket_send instead of sysread and
syswrite?

Aaron