Ioannis Zannos <[EMAIL PROTECTED]> wrote: > > Jochen: > > > Are the images serving through ApplePWS? If so, this seems weird. > > coweb.cc.gatech.edu serves the images lightning fast under ApplePWS. > > Coweb is an 80 MHz PPC601, so I think your 400 MHz G3 should blow it out > > of the water. > > The images are now serving through ApplePWS. > They come faster when they do, but sometimes > I have to repeat the request to have all of them loaded. > > More important: > > FOR EVERY SINGLE NEW PAGE I AM ACCESSING > ON THE SWIKI, I HAVE TO REPEAT THE REQUEST TWICE. > Actually, I've seen this on minnow, which (I think) is a 300-400MHz G3 . If you save a large page, then the socket seems to get closed before all the data comes back. The page actually does get saved, but the client doesn't get to see it. That's why saving it a second time would generate an edit conflict. This problem would be worse on faster servers, because they can close the socket faster :) Overall, closeAndDestroy: is supposed to avoid this problem. I remember at one time that the delay was turned way down in closeAndDestroy: in Comanche. Is that currently the case in Comanche/ComSwiki? Lex
