Thread View: alt.games.gb
2 messages
2 total messages
Started by Roger Lewis
Wed, 30 Dec 1992 07:09
tac command
Author: Roger Lewis
Date: Wed, 30 Dec 1992 07:09
Date: Wed, 30 Dec 1992 07:09
13 lines
924 bytes
924 bytes
If I'm at a stellar scope and type: tac d why does the server insist on giving me tac reports for all the planets in the system in addition to the tac for the destroyers? I find this a bit annoying, particularly since I'd like to do one big "tac d" at universal scope and detect anything I can blow up WITHOUT getting an <output flushed> message due to all the planetary tactical reports filling up the (client's?) buffer. By the way, is there a setting that allows that buffer to be larger? Is <output flushed> a message that is generated by the client or the server?
Re: tac command
Author: A Ghost Walking in the Shadows
Date: Thu, 31 Dec 1992 08:39
Date: Thu, 31 Dec 1992 08:39
20 lines
1283 bytes
1283 bytes
In article <23129@venera.isi.edu> rlewis@venera.isi.edu (Roger Lewis) writes: > >By the way, is there a setting that allows that buffer to be larger? > >Is <output flushed> a message that is generated by the client or the >server? The <Output Flushed> is SERVER generated. Not client generated. It is technically possible to overflow gbII's buffer, but it would lock up the client since it would be stuck in a read call. The server-client protocol calls for every line to be newline terminated and at present has kept lines to less than 1024 bytes. Except for map/orbit data but the client handles these differently so as to avoid any problems. The server should write() the output to the person's file descriptor instead of putting the <Output Flushed>. I've just never taken the time to fix this. >
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads