Fixed the problem dave reported yesterday, where a

large calendar hung the webcit renderer while displaying.
This turned out to have nothing to do with the size of the
calendar, but with a specific event that had no newline
at the end and caused the 000 terminator to appear at the
end of a line instead of on its own line.  Switched from
MSG0 to MSG4 in webcit to both work around this problem and
save over-the-wire chatter.   Dave's work from last night
plus this commit, resolve bug #284.

diff --git a/webcit/calendar.c b/webcit/calendar.c
index d9a3a247563d47828579edcd76ffcd1bdc426e39..6ea3cd7ffce570da8d96bdf8cfc6ddeb5e8b70a9 100644 (file)
--- a/webcit/calendar.c
+++ b/webcit/calendar.c
@@ -779,7 +779,7 @@ void display_using_handler(long msgnum,
        icalcomponent *cal, *c;
 
        relevant_partnum[0] = '\0';
-       sprintf(buf, "MSG0 %ld|0", msgnum);     /* unfortunately we need the mime headers */
+       sprintf(buf, "MSG4 %ld", msgnum);       /* we need the mime headers */
        serv_puts(buf);
        serv_getln(buf, sizeof buf);
        if (buf[0] != '1') return;

diff --git a/webcit/messages.c b/webcit/messages.c
index 1160e7dfbfe7f513de9856a90420b9438948e48a..b50d09250532e9066c053d87a857f3a3b4cffb3e 100644 (file)
--- a/webcit/messages.c
+++ b/webcit/messages.c
@@ -2559,7 +2559,6 @@ void readloop(char *oper)
 
 
 
-
        for (a = 0; a < nummsgs; ++a) {
                if ((WCC->msgarr[a] >= startmsg) && (num_displayed < maxmsgs)) {