I'm doing basically what you're doing. I haven't found a better way to do it either. Debugging a misplaced semicolon or similar that makes the worker JS invalid is a challenge.
rob On Mar 17, 5:46 am, Tibo <[email protected]> wrote: > Hello everyone. > > I have been playing a while with workerpool trying to synchronize > databases etc. > I am using firebug as a debugger. > > I encoutered a major problem which was no indication of what's going > on within the worker. > For example, while I still had errors in my code, the only error > message appearing in firebug console was "Error in worker 1. Could not > process message because worker does not have an onmessage handler". > > Even trying to debug step by step, instruction by instruction, it > seemed I finally got into a compiled javascript (???) which actually > was the worker itself. Thus, not a good way to debug. > > I finally found where my coding errors were and tried to see what was > happening in my worker. Since a worker child has non access to DOM, > the only way I found was to catch exception and send them back to the > parent worker. Is this the only way to do it ? > > Is there any other ways or any improvements I am not aware of about > this ? > > Thanks.
