Dismissing dialogs (was 2.1b3 --> way slow)

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 15185
interpreted = N
texte = >Grant mentioned a few weeks back that this signal raised error was >traced to a WebCat memory leak. Subsequent 2.1 revs were suppose to >have fixed that, but there is this slowness problem in 2.1b2 and b3 (at >lease with the cgi) which is much more of a problem than the occassional >signal raised error. The problem is that the signal raised error dialog >box requires you clik OK to make it go away (okey dokey doesn't work on >it either) and while the dialog is on screen the server is frozen. And >MacsBugs and PowerKey do not sense it as a hang so the server just sits >there in suspended animation until we notice it.Ah, now I remember your posted messages from a few weeks ago.Well, just imagine having your server colocated somewhere else, and then imagine that server having no monitor attached to it. That's my situation right now. So not only do I *not* have the benefit of being able to look at my own server, but if this kind of thing happened at my co-location site, the people there would never see it no matter how much they happened to me looking at my servert, because there's no monitor on it!This creates a serious situation to have to deal with when your livelihood is based on the server being able to run by itself -- or at the very least, to be able to reset itself when things mess up. MacsBug and PowerKeys can only do so much ...>We have not traced >this to any specific condition which causes the signal raised error so >it is not reproduceable. We have not been able to isolate a particular >template which causes this, and we've been running in WebCat debug mode >in an effort to track it down, too. It just seems to happen at the most >inopportune times...The speed problem went away on my Mac as soon as I replaced the 2.1b2 plugin with the 2.1b3 plugin, and I haven't used the CGI for a very long time, so if the slowness problem still exists in the CGI, it's apparently still there only in the CGI, because the plugin seems to fly.I've never seen the signal raised error dialog ... but if that dialog were a modal dialog box, Okey Dokey should take care of it. But Okey Dokey can only dismiss modal dialog boxes, and some programs create non-modal dialog boxes ... which means Okey Dokey is no good with them. Apparently WebCat does not create modal dialogs ...Maybe Grant can make that dialog modal in the next revision, then at least Okey Dokey can deal with this, even if it won't actually resolve the problem. I've always felt that server software should not post any dialong, instead it should write these errors to a text file. But if there's some reason it MUST post a dialog, that dialog should be able to be dismissed automatically, either by Okey Dokey, or by another utility, or by the software that puts the dialog there in the first place.Eudora is not server software, but it also has a feature that allows you to choose whether or not to dismiss its non-modal dialogs automatically after a user-configurable period of time. Maybe the same thing can be done with WebCat in the future, especially if dialogs cannot be replaced by appending the message to a text file and if there's no other way to create WebCat dialogs that Okey Dokey can dismiss ... :)Sincerely, Ken Grome WebDNA Solutions http://www.smithmicro.com/webdnasolutions/... Associated Messages, from the most recent to the oldest:

    
  1. Re: Dismissing dialogs (was 2.1b3 --> way slow) (Karl Schroll 1997)
  2. Dismissing dialogs (was 2.1b3 --> way slow) (Kenneth Grome 1997)
>Grant mentioned a few weeks back that this signal raised error was >traced to a WebCat memory leak. Subsequent 2.1 revs were suppose to >have fixed that, but there is this slowness problem in 2.1b2 and b3 (at >lease with the cgi) which is much more of a problem than the occassional >signal raised error. The problem is that the signal raised error dialog >box requires you clik OK to make it go away (okey dokey doesn't work on >it either) and while the dialog is on screen the server is frozen. And >MacsBugs and PowerKey do not sense it as a hang so the server just sits >there in suspended animation until we notice it.Ah, now I remember your posted messages from a few weeks ago.Well, just imagine having your server colocated somewhere else, and then imagine that server having no monitor attached to it. That's my situation right now. So not only do I *not* have the benefit of being able to look at my own server, but if this kind of thing happened at my co-location site, the people there would never see it no matter how much they happened to me looking at my servert, because there's no monitor on it!This creates a serious situation to have to deal with when your livelihood is based on the server being able to run by itself -- or at the very least, to be able to reset itself when things mess up. MacsBug and PowerKeys can only do so much ...>We have not traced >this to any specific condition which causes the signal raised error so >it is not reproduceable. We have not been able to isolate a particular >template which causes this, and we've been running in WebCat debug mode >in an effort to track it down, too. It just seems to happen at the most >inopportune times...The speed problem went away on my Mac as soon as I replaced the 2.1b2 plugin with the 2.1b3 plugin, and I haven't used the CGI for a very long time, so if the slowness problem still exists in the CGI, it's apparently still there only in the CGI, because the plugin seems to fly.I've never seen the signal raised error dialog ... but if that dialog were a modal dialog box, Okey Dokey should take care of it. But Okey Dokey can only dismiss modal dialog boxes, and some programs create non-modal dialog boxes ... which means Okey Dokey is no good with them. Apparently WebCat does not create modal dialogs ...Maybe Grant can make that dialog modal in the next revision, then at least Okey Dokey can deal with this, even if it won't actually resolve the problem. I've always felt that server software should not post any dialong, instead it should write these errors to a text file. But if there's some reason it MUST post a dialog, that dialog should be able to be dismissed automatically, either by Okey Dokey, or by another utility, or by the software that puts the dialog there in the first place.Eudora is not server software, but it also has a feature that allows you to choose whether or not to dismiss its non-modal dialogs automatically after a user-configurable period of time. Maybe the same thing can be done with WebCat in the future, especially if dialogs cannot be replaced by appending the message to a text file and if there's no other way to create WebCat dialogs that Okey Dokey can dismiss ... :)Sincerely, Ken Grome WebDNA Solutions http://www.smithmicro.com/webdnasolutions/... Kenneth Grome

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Include a big block of text (1997) [delete] problem (1997) Separate SSL Server (1997) Upgrading old WebCat Database Files (1997) db creator (2000) [WriteFile] problems (1997) Which GUI HTML editors work with WC ? (1997) WCS Newbie question (1997) Question... (2002) Can't use old cart file (was One more try) (1997) price totals (2003) Enhancement Request for WebCatalog-NT (1996) [WebDNA] Webserver does not respond occasionally (2018) WebCat2b13 Mac plugin - [sendmail] and checkboxes (1997) Webmerch Error (1998) browser info.txt and SSL (1997) PCS Frames (1997) [AppendFile] problem (WebCat2b13 Mac .acgi) (1997) Trouble with formula.db (1997) Fun with Dates - revisited (1997)