Alejandro,
We've observed a similar problem, but only on our friend's computer
running Windows 2000. We hypothesized that Win2K was overwhelming
ComSwiki with a lot of requests in a rapid succession. We further
theorized that there was a bug in Comanche that didn't properly
manage resources (perhaps Sockets), a problem that was taken care of
by finalization, but only in the long run.
That said, I'm currently working on tracking down resource usage AND
getting some of HTTP/1.1 functionality into Comanche. Persistent
connections, I believe, could make serving pages with lots of images
much smoother. (some indirect evidence for that is in the tests that
I've ran recently, see my previous postings on the list). Further,
identifying the resource leak/mismanagement could make ComSwikis much
more stable.
As much as I'd like to find these bugs, I won't mind if somebody else
on the list beats me to fixing them.
Bolot
