Dear gnoga folks, I have encountered some timeout problems executing Gnoga.Server.Connection.Execute_Script. If I understand the code correctly, this function tries to execute a script with a fixed timeout (3 seconds) If this execution reaches this timeout it *executes again* the script.
Some thoughts and questions: - I have seen this fail under some circumstances: heavy load of script executions with Firefox as client. I haven't be able to reproduce with other clients. I don't know if I'm doing something *peculiar*. Does anyone had similar behavior? - Three seconds seems a small timeout to me and a hardcoded one. Yes, I can modify as I want, but I wonder if this parameter could be passed as parameter of the Execute_Script function. If you like this approach and if it is useful for some people I can send a patch, it seems easy to implement (maybe with 3s default parameter in order to keep backwards compatibility, maybe a setter to the global variable, maybe the combination of the two approaches is the best...) - On the other hand the subsequent execution to a timeout seems a little risky to me. It assumes the idempotence of the executed script (a hard assumption? I agree that most of the calls are getting/setting properties and styles, so it fulfills idempotence, but the direct call still exists... and it is very useful to me) I will be pleased to hear experiences and comments about Execute_Script... Best Miguel Ángel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list
