src/sbbs3 msg_id.c 1.6 1.7 msgtoqwk.cpp 1.46 1.47 pack_qwk.cpp 1.72 1.73 pack_rep.cpp 1.43 1.44 postmsg.cpp 1.104 1.105 qwk.cpp 1.75 1.76 sbbs.h 1.437 1.438 un_qwk.cpp 1.48 1.49 un_rep.cpp 1.60 1.61
Update of /cvsroot/sbbs/src/sbbs3
In directory cvs:/tmp/cvs-serv13035
Modified Files:
msg_id.c msgtoqwk.cpp pack_qwk.cpp pack_rep.cpp postmsg.cpp
qwk.cpp sbbs.h un_qwk.cpp un_rep.cpp
Log Message:
Solved the networked-voting "ordering problem". QWK/REP packets that contained normal messages along with voting data (polls, ballots, etc.) would always be imported in this order: msgs, polls, ballots/votes, and then poll-closures. This could result in a confusing order of messages in the local msg base where there were messages in reply to a poll before the poll appears and other oddities. Anyway, this is now resolved by placing a msg "header block" for each vote-data item in the MESSAGES.DAT file. Since there is no body/text blocks,
it should be ignored under normal circumstances, but these header blocks are only created if VOTING.DAT is enabled anyway.
And now, the VOTING.DAT contains an extra line (empty .ini section) with the HEADERS.DAT offset associated with the chronology of the item. The format
is still backwards compatible with the earlier builds that included VOTING.DAT support.
Also, fixed the vote/poll/closure Message-IDs containing a msg number of 0 (while not technically a problem, it wasn't the intention) with the use of the new function: get_new_msg_number().
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ
telnet://vert.synchro.net