0

callback behaviour?

I'm dealing with asynchronous threaded network code that needs to callback to the browser every now and again.

I thought that if I pass a callback to a Ruby method, and never call trans.complete, then I could invoke that callback again and again.

However, I'm getting Ruby segmentation faults when I invoke that callback:

2009-06-13 10:31:35Z [2574:0xb0081000] ERROR - redirectStdHandles: (eval):45: [BUG] Segmentation fault
ruby 1.8.7 (2008-06-20 patchlevel 22) [i686-darwin8.11.1]

Is there a better way to callback to the browser? I notice some of your libs take DOM ids, so I presume they can communicate with the DOM?

1 Reply
  • Have worked out what the problem was, the hash I was sending had symbols in it.

    QUOTE (alexandermaccaw @ Jun 13 2009, 02:35 AM) <{POST_SNAPBACK}>
    I'm dealing with asynchronous threaded network code that needs to callback to the browser every now and again.

    I thought that if I pass a callback to a Ruby method, and never call trans.complete, then I could invoke that callback again and again.

    However, I'm getting Ruby segmentation faults when I invoke that callback:

    2009-06-13 10:31:35Z [2574:0xb0081000] ERROR - redirectStdHandles: (eval):45: [BUG] Segmentation fault
    ruby 1.8.7 (2008-06-20 patchlevel 22) [i686-darwin8.11.1]

    Is there a better way to callback to the browser? I notice some of your libs take DOM ids, so I presume they can communicate with the DOM?
    0
This forum is locked.

Recent Posts

in Support & General Questions