Sure, feel free to do what you are comfortable with. I just couldn't
understand why there is a need for the Update function at all.
Hope that your Go transition goes smoothly :)
-Agniva
On Thu, 27 Sep 2018 at 21:29 Michael Ellis
wrote:
> Thanks for the feedback, Agni. I think I may not have i
Thanks for the feedback, Agni. I think I may not have included enough
detail in my original post.
At present, the app is in the middle of transitioning to an all-Go
implementation. For business reasons, that process will be stretched out
over the next several months or longer. In the meantime,
I think you are overcomplicating this a bit. It seems like a simple pattern
of broadcasting a change to multiple agents. You send the change over a
REQ-REP pair, and broadcast it to others over a PUB-SUB pair.
Why do you need to copy the struct again ? Just get the struct from the REP
socket an
A map[string]interface{} can hold an arbitrary, string labeled collection
of any types. You just need to have a type switch and cover all the
possible inputs for it.
The concurrency is safe as long as only one process is writing to variables
at once. If you need multiple concurrent processes to
