[Seaside] Seaside application hangs on file upload

[Avi Bryant]

On Sep 21, 2004, at 4:14 AM, Colin Curtin wrote:

> The times that I have had it hang on me, I found that the SocketStream
> (in Kom) was stuck on #upToAll: which, out of the box, is horrendously
> inefficient. Hopefully it's been fixed by now.

Kom is essentially unmaintained right now, since Stephen is busy with  
other things - so there hasn't been any new release for that to be  
fixed in.  However, there was a fix posted on this list a while back:

http://lists.squeakfoundation.org/pipermail/seaside/2004-April/ 
002719.html

If anyone's having trouble with uploads I would try applying that fix  
first.

There's definitely an open question of what we should do about Kom -  
unless Stephen steps in to say that he's suddenly got a lot more time  
to be an active maintainer, we need to either:

a) fork a version of Kom for use with Seaside, and start releasing  
updated versions again
b) heavily patch Kom from within the Seaside package
c) move to Swazoo as the default Seaside webserver - to try this,  
install Swazoo-HTTP and Swazoo-Listener from SqueakMap and evaluate  
"SeasideSwazoo startOn: 9090".  I don't think this solution is quite  
ready for prime time yet, but it probably wouldn't be that hard to fill  
in the holes (one of which, IIRC, happens to be file uploading...).

Thoughts?
Avi