🚀 go-pugleaf

From: Marshall Rose <mrose@UDel-Dewey.arpa>

    I think the best solution is to have the imagen tell the host how
    many page images it processed and how many pages it printed.  I am
    told that when you connect the imagen to a host with a serial line,
    that you get back some sort of accounting information (I don't know
    what; we use the ethernet option and are very happy with it, thank
    you).  

    I think the reason that the imagen does not return this info via
    the ethernet is that it closes the connection before it's done
    printing the job (presumably after it's snarfed the imPress EOF or
    gets a TCP FIN or whatever).  Why it does this, I don't know.
    However it won't accept a new connection from the net until the
    first one is closed.  After accepting a new connection, it blocks
    until the job header for the first job is printed.  After that data
    is read from the new connection.

    Perhaps someone who knows something about the TCP/IP implementation
    for the Imagen can shed some light here?

/mtr