Pattern for interacting with the main thread about react-native

[jlongster]

Oh haha. RTFM. It's actually pretty simple:

- (void)loadMesh:(NSString *)path {
    RCT_EXPORT();

    dispatch_async(dispatch_get_main_queue(), ^{
        node.mesh = [REMeshCache meshNamed:path];
    });
}

That works!

[vjeux]

If you are bored, would be awesome to compile this into some sort of docs :)

[jlongster]

If you are bored, would be awesome to compile this into some sort of docs :)

I almost filed an issue about that, actually! I was going to ask if there's a place you want us to contribute to docs. I can certainly write done a bunch of small stuff I've learned. Where would you like it, and what format?

[vjeux]

We're going to have official docs before we open this repo to everyone. They'll be in the docs folder in markdown, the same way React is. If you can start writing them in markdown and in the docs folder with whatever you think is useful for people, that would be awesome!

https://github.com/facebook/react/tree/master/docs/docs

[frantic]

Looks like this is a very common pattern - native modules that run on main thread. Maybe we could do something like:

- (void)loadMesh:(NSString *)path {
    RCT_EXPORT_ON_MAIN_THREAD();
    node.mesh = [REMeshCache meshNamed:path];
}

@a2 / @nicklockwood - any thoughts?

[a2]

The JS bridge is meant to be asynchronous and therefore runs off the main thread. I personally think that if something should happen on a specific thread/queue, it is the caller's responsibility. Apple's documentation often says that callbacks can happen on private threads/queues and that you should dispatch if necessary.

[frantic]

@a2 great answer, totally makes sense!

[nicklockwood]

Whilst @a2 is quite correct, I wonder if it might make sense to change the thread that we call back to modules on to main.

We don't call module methods on the JS thread, we actually call them on the shadow thread, which is a seperate thread used by the RCTUIManager to do layout calculations.

But other than the UIManager, the vast majority of modules either don't care what thread they run on, or would prefer to run their methods on the main thread. Perhaps then, the bridge should call back to main, and the UIManager can dispatch to the shadow thread?

It would save having to dispatch_async inside every single module's methods for the sake of catering to the requirements of one specific module.