PizzaWizard
Understanding COM interface references for an ASP.NET REST API...
(Except of course, for the fact that I'm using a single computer spawning multiple COM applications to act as a backend for a web app and ignoring the stateless part of REST entirely)
10 replies
Understanding COM interface references for an ASP.NET REST API...
The server will persist across multiple user connections, it essentially never turns off.
So do I just give every user a token, and then store that in a dictionary with their
remoteControl object?
My question would then be, if I wanted to let a user execute a command like
remoteControl.StartSimulation() to start a new simulation on their specific instance, I could just pass the user's token and say something like userMap["thisUserToken"] and get back a specific remoteControl object? I was concerned that I would just be passing the reference to the same remoteControl back and forth...10 replies
Understanding COM interface references for an ASP.NET REST API...
Hit the limit on the previous message. Happy to read up and educate myself instead of just waiting for someone to write code for me, but there's a LOT of documentation on COM/OLE, and it's pretty overwhelming for someone who doesn't spend any time in low-level systems/OS programming or C/C++.
Would be happy to be pointed in the right direction to get signal from the noise. Thanks!
10 replies