Sync Config Pins in a Boygroup Setup

right now config pins are ignored in a boygroup setup. i regard it as useful to have this information mirrored on all clients. every change/write to a config pin should be reflected on the clients.

does someone rely on the current behaviour ?

@devs, this can be alot of data, in my case its a large XML, would this be a problem ?

and second, what happens if the node on the server writes to a config pin, boygroup syncs this to clients and clients may write to their config pins as well. would this be a conflict? who comes first ? just thinking about possible bugs.


thanks u7. this is tracked

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.