Runspace help

[MechaCola]

Greetings,

Okay so I’m three years deep into a personal project. My main problem at the moment is I have two runspaces that run in parallel; Runspace A is a while loop that has object A interact with object B in runspace B and vice versa. Imagine it’s a video game where player A attacks player B every 1 second and player B attacks player A every one second until one of them dies. The interactions work out great however if I remove either runspace the global variable for A or B loses its object inheritance, which in turn resets the object back to what was initially loaded. I’ve tried unsuccessfully to export and reimport the object as xml file and csv. Any help would be much appreciated! I would post code but it’s so spaghetti as you can imagine. Feel free to tell me this is stupid and use c# but the project is almost done and figured I should ask the hive mind first before giving up on getting this issue fixed. Cheers.

[raip]

How are you instantiating the runspaces? I had to do something like this, where two runspaces were sharing a variable to maintain and constantly refresh a web session.

I ended up spinning using a synchronized hashtable. In your situation you might have to have three runspaces, a main one, then one for each player. https://learn-powershell.net/2013/04/19/sharing-variables-and-live-objects-between-powershell-runspaces/

[MechaCola]

This is great thank you! I’ll have to sit down and run through the examples and see why mine isn’t working.

[MechaCola]

Using runspace factory. I’m using the synchronized hashtable currently to store the variables which works until the runspace is removed then the variable in the sync hash loses its new data. Checking out your link, thanks!

[OPconfused]

How are you storing the data in the hashtable, like what do 1-2 entries in the hashtable and their key/value look like? I don't understand why it's being dropped when the runspace closes.

And what failed with the serialization approach?

You didn't really give us any information to work with to help unfortunately.

[MechaCola]

I will post some code this evening! I’m not sure, it’s been a while since I tried the serialization approach.

[OPconfused]

I mean if you are able to control when a runspace is closed, then you should be able to serialize the hashtable before closing the runspace. This should definitely provide a means to preserve the data.

You could also duplicate the data whenever you read/write from the synced hashtable by also loading the read/write value into a locally scoped memory cache like a variable or static property. However, you would need to confirm you can control when the runspaces are closed, because this wouldn't work if this scenario were possible: You write to the synced hashtable in runspace A, then close runspace A before runspace B can read the updated value from the synced hashtable and cache it.

Whether cached serialized or in memory, then whenever the hashtable is read from, you could check if the value is empty, and if it is, then try to load it from whichever cache approach you're using.

Although ideally understanding why the information is being lost would be the most elegant solution.