[Red5devs] Problem with shared object security?

[Jeremy Morton]

Hi,

In Actionscript 3, when I try to create a remote shared object and 
connect() to it, I'm having a slight problem.  This is the kind of code 
I'm using:

var so:SharedObject = SharedObject.getRemote("moo", nc.uri, false);
so.addEventListener(NetStatusEvent.NET_STATUS, netStatusHandler);
so.addEventListener(AsyncErrorEvent.ASYNC_ERROR, asyncErrorHandler);
so.addEventListener(SyncEvent.SYNC, soSyncHandler);
so.connect(nc);

When I implement my Red5 ISharedObjectSecurity to allow the client to 
create and connect to the requested object (ie. returning true), my 
soSyncHandler receives a SYNC event and all is well.  However, when I 
implement it to deny the client the ability to do either of these (ie. 
return false), nothing happens on the client side.

Why is this a Red5 issue and not an AS3 issue?  This seems like strange 
behaviour for Adobe to implement, not being able to receive any 
notification about the SO not being successfully connected to.  Could it 
be that FMS sends an event (probably a NetStatusEvent) when the 
.connect() call fails, but Red5 is not doing so?  Anyone with FMS 
experience able to tell me how you're meant to detect if a SharedObject 
connect() fails?

Best regards,
Jeremy Morton (Jez)