RE: [Webware-discuss] Action behavior/issues

2002-07-22 Thread Karl Putland
On Mon, 2002-07-22 at 00:04, Matt Feifarek wrote: | 1. Multiple submit buttons on the same page and submit with Enter. | Problem: Browsers have undefined behavior with regard to multiple submit | buttons on the same form. Some of them provide the name=value pair of | the first submit button

RE: [Webware-discuss] CVS Update: Page.endResponse()

2002-07-22 Thread Geoffrey Talvola
Matt Feifarek wrote: | - If called from within an awake() or sleep() method, it immediately skips | all further awake(), respond(), and sleep() processing and sends the | accumulated response. Shouldn't it still call sleep? Usually, one subclasses Page and has something like this in

RE: [Webware-discuss] CVS Update: Page.endResponse()

2002-07-22 Thread Matt Feifarek
| If you're within awake() and you need to skip the respond() but you still | want sleep() to be called, you can just call it yourself: Well, sure, but you can do the same thing in response() ;-) I'm not trying to be annoying, or anything, but consistency seems like a good idea for something

RE: [Webware-discuss] CVS Update: Page.endResponse()

2002-07-22 Thread Geoffrey Talvola
Matt Feifarek wrote: | If you're within awake() and you need to skip the respond() but you still | want sleep() to be called, you can just call it yourself: Well, sure, but you can do the same thing in response() ;-) True. In response() it would always be safe to call

Re: [Webware-discuss] MiddleKit Threading Problem - Stage 2

2002-07-22 Thread Roger Haase
Well, I have been wrong a lot lately... My HTML page had 7 very similar img src=ShowPix?pid=4tn=160 tags trying to display 7 images. The second image succeeded and the other 6 failed. If I had messed up the classes.csv file all seven images should have failed. Also, restarting the

RE: [Webware-discuss] CVS Update: Page.endResponse()

2002-07-22 Thread Matt Feifarek
| See the problem? If SitePage.awake() calls endResponse() then Yeah. It seems there's no sure fire way to do it. You either run the risk of calling it when you shouldn't or not calling it when you should. It's up to the servlet author to be rigorous... maybe an exception could be introduced