🚀 go-pugleaf

In article <1992Dec30.204220.9141@apgea.army.mil>, rcmerrit@apgea.army.mil (Robert C. Merritt <rcmerrit>) writes:
|> Question: Does WildCat still have that horrable message base system? I
|> was on "the" wildcat board for this area a while back. (It was the test drive
|> version BTW) And if there were replys to a message, you HAD TO read all
|> the messages in that thread before going to the next message. If there
|> were 20 some replys to a message about cross stiching, you were stuck reading
|> those things! I though Wild Cat was well done and I've always heard they
|> were well supported but the message base gave me the shivers!

I would imagine the simple answer would be no, it isn't still that way, but 
honestly, in the 3+ years I've been running a Wildcat system, the message 
system NEVER operated in that manner. This would take me back to version 
2.10, and the test drive release at that time, (late 89/early 90), which
was based upon release 1.13. You do have the option of reading replies in 
order when reading messages, but it is not the default mode of operation
for reading messages. The default mode is non-threaded, sequential reading, 
and effective with version 3.00 of Wildcat, each message area is an individual
B-tree indexed database (prior versions kept one database combining all message
areas). The concept of joining conferences (or sub-boards) was introduced
in V3.0.
Cheers,
Kevin 

-- 
Kevin Brokaw   (kevinb@csd.sgi.com)     | 
Product support engineer                | Sorry, this closet is for anxieties.
Silicon Graphics Computer Systems       | Pipe dreams are under the bed. 
(Forgive them,they know not what I post)|