If you’re using Remote Shared Objects (RSO’s) in conjunction with Flash Media Server 3 (FMS3) and having trouble getting the SyncEvent to fire after one of the RSO’s gets updated, then you’re not the only one. I struggled with this issue for an entire day, making it worthwile to write about it.

According to Brad Outlaw, software developer at Adobe, the main “live” application that  gets shipped with FMS3 has a restriction by default – which goes for all signed applications – preventing write access to the application, including Shared Objects. Therefore you need to replace the file named “main.far” (default location is “C:\Program Files\Adobe\Flash Media Server 3\applications\live”, back it up!) with a new file “main.asc”. This is just a simple textfile with the following code:

application.onConnect = function (clientObj) {
	return true;
}

Ofcourse you can also create a new application folder and simply put the main.asc file in there. There, problem solved!

Remember that if you’re using RSO’s of a complex datatype (everything that’s not a string or a number) you need to call the setDirty() method after udpating the RSO to trigger the SyncEvent on the clients.