I am integrating the Web Service and the Actor Framework on a cRIO. When the Web Service is started, it launches the root level of the Actor Framework. My philosophical problem is that web services needs to be able to return information that the Actor Framework possesses. This means needing to call the framework with a message and waiting for a response. I agree that it is a bad idea to send a message and wait for a response. I have come up with two options for a solution. The first is to pass a queue created, by the web service, to the framework that is monitored by the web service. This way if the framework takes to long to respond, an error message can be passed back by web service. The second is to move the needed information from the framework to the web service or making it a global. The draw back here is that it loses some of the methodology of encapsulation.Since I have limited experience with the Actor Framework, I am open to suggestions before I spend much more time programming this aspect of the code.Thanks,Eldon

Actor Framework Discussions

Web Service & Actor Framework

If you don't want to use "send message and wait for reply", what about registering and braodcasting? I like it as it's general and non blocking (though if you do need the process to block, send and wait for reply makes more sense).

Basically, whoever wants to know when data is changed "registers" in the data actor; whenever data is changed, the data actor sends the updated data to all registered elements. The boradcast can also be via HTTP etc. if you want.

Thanks,

Danielle

"Wisdom comes from experience. Experience is often a result of lack of wisdom.”
― Terry Pratchett