Is it valid to retain arguments from CefV8Handler::Execute?

[ScottKevill]

Is it valid to retain the arguments CefV8ValueList outside of CefV8Handler::Execute?

Essentially, I'm wanting to handle the native JS function processing on another thread (return values are not needed), and it would be very convenient to just copy the arguments list. From inspection, it seems that the refcounts for all CefV8Values are being correctly managed, but I'm wondering if it's the GC that is biting me.

Edit: The arguments in this case are only basic JS types (bool, int, string) if that matters.

[magreenblatt]

The refcounting implementation is thread safe (so you could pass a reference to another thread and then back to the main thread), but you can't call CefV8Value methods on other threads.

[ScottKevill]

Okay, yeah, that's what I'm seeing. I'm using multi_threaded_message_loop with MFC so in this case, the UI thread is not the main thread, which is what is making this inconvenient.

Does that also mean I cannot even (painfully) re-create a copy of the list values (eg. IsBool + GetBoolValue + CreateBool)? A pity to not be able to re-use such a flexible method for marshalling.

[magreenblatt]

If you're using CEF3 you can convert to something like CefListValue (from cef_values.h) which is thread safe.

[ScottKevill]

Oops, I should have mentioned that I'm using CEF1. That's okay, I don't have very many native functions to worry about, so I'll package them manually. Thank you for the quick responses.