zeep: not sure if you can stop the client from dumping data on the webserver, but you can at least signal "stop doing that to the ua" by doing $self->render(text => 'Yikes!', status => 400); # or some other status

batman: yeah, the streaming event-based code was what i was hacking; if the FS got full my stuff simply doesn't write to disk but allows the rest of the streaming to happen. I think if i tried to render error halfway thru, I'm afraid the transaction states will just get screwed up. so wondering if there's a neat way to cancel halfway thru

in my case, the "normal" situation (when i'm not using the streaming), mojo feeds the chunks into asset; sometimes dies with "Out of memory" on my system which is a memory-constrained one :) so i was wondering if there was another way out

In a pre-forking server, is it possible that the parent process calls rand (which calls srand) and then whenever the child processes call rand thereafter, they will generate the same random numbers? (since srand has already been called once before the children were born)?