COBOL .NET and RunUnit

Serveral questions here all in regard the the RunUnit in COBOL .NET.

1. In COBOL .NET you can spin up a RunUnit and do work, then suspend the RunUnit in a rununitcache (ConcurrentDictionary).
A ConcurrentDictionary is stored in process, is there any way to store a suspended RunUnitin Redis or something similar?

So if you are scaling out across servers you could pick up that RunUnitregardless of the server you hit via it's id or something?

2. What else could I do with a RunUnit other than start, stop, dispose, SetUserData & GetUserData that might add value?

3. Can you get the ID of a RunUnit inside the RunUnit?

4. Is there a limit to amount of RunUnit's you can spin up under say C# rest api?

Neil

------------------------------
Neil Hayes
Software Development Specialist

------------------------------

1) Sorry, it is not possible to serialise a RunUnit to store it in redis (or anything else)
2) You have the CBL_ apis, that can be used to get/set user name:

• CBL_MANAGED_SESSION_GET_USERDATA
  Retrieves user data saved in the current RunUnit.
• CBL_MANAGED_SESSION_SET_USERDATA
  Sets user data in the current RunUnit.
  
  

3) Yes but it is not documented, contact Scot Nielsen and start a conversation about it, mention me and I will contribute the technical information
4) You would need to monitor/size your memory usage to determine this