server and client associate buffer lines using a unique(within a buffer) ID
number, and an integer offset.

no need for tracking message IDs

Buffer operations: (messages from server, telling client something happened to
the buffer)
"There is a new buffer named xxx"
"The buffer named xxx has been deleted"

<!-- newbuffer does not tell the client about content of the buffers.
The client has to take control and ask for that.  newbuffer is also
not recursive. 
 
type=<random string>
  The type identifies the relationship of the buffer to
  its parent buffer.  The client is expected to know what
  that relationship is (in terms of UI layout and perhaps
  style), and the server is expected to be consistent
  about associating a type string with any given buffer.
-->

(response to client request for root buffers)
<newbuffer name="f00f.net" type="a" />
<newbuffer name="irc.undernet.org" type="a" />
<newbuffer name="icq.mirabilis.com" type="b" />

(response to client request for buffers in "f00f.net")
<buffer name="f00f.net>
	<newbuffer name="bytesex" type="d" />
	<newbuffer name="f00f" type="d" />
	<newbuffer name="xenocide" type="d" />
</buffer>

(response to client request for buffers in "xenocide")
<buffer name="f00f.net">
	<buffer name="xenocide">
		<newbuffer name="userlizt" type="k" />
	</buffer>
</buffer>

(response to client request for content of "f00f.net/xenocide")

<buffer name="f00f.net">
	<buffer name="xenocide">
		<append>
			<bufferline id="194">
				<line>Hi</line>
			</bufferline>
		</append>
	</buffer>
</buffer>

(response to client request for content of
"f00f.net/xenocide/userlizt")
<buffer name="f00f.net">
	<buffer name="xenocide">
		<buffer name="userlizt">
			<append>
				<bufferline id="0">   <line>Xenoc</line> </bufferline>
				<bufferline id="1337"><line>[Jane]</line></bufferline>
				<bufferline id="2">   <line>repp</line>  </bufferline>
			</append>
		</buffer>
	</buffer>
</buffer>

(response to client request for viewing id of "f00f.net/xenocide")
<buffer name="f00f.net">
	<buffer name="xenocide">
		<viewing id="194194" />
	</buffer>
</buffer>

<!-- goodbye! Note: Recursive toast. -->
<removebuffer name="f00f.net" />


Note: These following operations do not cause id numbers to be inserted or
deleted, rather, what datum is associated with what id is changed.
"This buffer has had n lines removed from the end"
"This buffer has had n lines from position x moved +/-y lines"
	(Leave the data alone - as in - lines that are "exposed" are left.)
"This buffer has new data starting at line n (overwrite)"
"This has been appended to the buffer"

To insert a user in the middle of a userlist buffer..  The userlist
buffer has a first id of 0, all the ids are sequential, and there are
15 elements in the list.  
(Note atomic operation)
<buffer name="f00f.net" >
	<buffer name="xenocide">
		<buffer name="userlizt">
			<append>
				<bufferline id="15">
					<line></line>
				</bufferline>
			</append>
			<!-- after the append, there are now 16 -->
			<!-- move 
				id=<first line to be moved>
				length=<required>
				distance=<+/- int>
		
				If elements are moved off the end of the list (the server
				should not send this command, but we shall define it anyway)
				then the elements are simply dropped and forgotten about
				(because they would no longer have a known ID).
			-->
			<move id="5" length="10" distance="1" />
			<!-- update
				id=<line to start replacing data>
			-->
			<update id="5">
				<bufferline>
					<line>Squint</line>
				</bufferline>
			</update>
		</buffer>
	</buffer>
</buffer>

Bye, squint...

<buffer name="f00f.net" >
	<buffer name="xenocide">
		<buffer name="userlizt">
			<move id="6" length="10" distance="-1" />
			<!-- remove
				count=<number of lines to remove from the end>
			-->
			<remove count="1"/>
		</buffer>
	</buffer>
</buffer>

Error, from server:
"ID requested not found.  topID=xxx bottomID=xxx"
(note : IDs are not greater than MAX_INT, may wrap)


Messages from the client:
ask for buffer list (optionally within buffer)
get viewing id
viewing id (tell server what line of buffer you're viewing)
get buffer content (id, and +/- count)
"click"
input string

(Sent upon connect)
<getbufferlist />

(Sent after the first buffer list has been recieved)
<buffer name="f00f.net">
	<getbufferlist />
</buffer>

(sent after f00f.net buffer list has been recieved)
<buffer name="f00f.net">
	<buffer name="xenocide">
		<getbufferlist />
	</buffer>
</buffer>

(sent when "xenocide" is first viewed (maybe the client has a -very-
short term memory...))
<buffer name="f00f.net">
	<buffer name="xenocide">
		<getviewingid />
	</buffer>
</buffer>

(sent when "xenocide" is first viewed (maybe the client has a -very-
short term memory...))
<buffer name="f00f.net">
	<buffer name="xenocide">
		<getbuffercontent id="194194" count="-25" />
	</buffer>
</buffer>

(blah blah, stuff's been appended. send server current viewing id.
If your viewing id is the last line in the buffer, the server should
automagicaly update your viewing id when a line is appended.)
<buffer name="f00f.net">
	<buffer name="xenocide">
		<viewing id="194198" />
	</buffer>
</buffer>

(input events are a plain text string the user types)
<buffer name="f00f.net">
	<buffer name="xenocide">
		<input>hello!!!!!!!</input>
	</buffer>
</buffer>