I have created a shiny app on the backbone of {golem} + {brochure}, both fantastic packages by @ColinFay. When using single R sessions as suggested in Chapter 16, it is better to use inner-session asynchronous code, so that users aren't blocked waiting for a render function.
In my case I have four modules that output a plot on a dashboard. I would like to send this plotting logic elsewhere while the user interacts with the app. Since brochure is natively a multi-session app infrastructure, is cross-session async capable of keeping users seperate being that it is two separate sessions, or will there still be issues between users on the same endpoint (session)?
TL;DR
Is each brochure page session restricted to one user? or as the docs say, is each page opened a new session and unique (thus only needing cross-session async) -- scroll down to design pattern here to see
brochurestructureDo I need to implement inner-session async code blocks with
promises+future?
I know this isnt the best SO question but I really could use some lexical insight!
