Authorize plugin notify, on connection timeout + remote function execution

Question

When a client application stops the stream I normally get an
E_STOP notify. But if a client dies due to network outage or the
client computer dies (or something other unforseen that doesnt give
a FIN/RST on the TCP connection), then it seems there is no way to
get a notification about this..
Or have I missed something?
If not, that is a big feature request for us, and probably
other people developing pay-per-view-stuff..
Also, is there some way to catch remote executions? Ie if my
client calls a function on my SSAS, can I catch that invocation in
my authorize module somehow? (Or in some other way get trigger some
code in my plugin, when a client calls a function)
Is there somewhere on the adobe site one can submit feature
requests to FMIS?
Thanks!

Answer 1

Hi, thanks for your answer!
Yes, that would be one solution that I've thought of.. But
then the question is how to interconnect SSAS/remote events with
the authorization plugin..
The only thing i've found is the addNotifyAction on
IFmsAuthEvent that allows me to call a a SSAS function from my
plugin (when I process an actual event). But not the other way
arround (dispatching an authorize/notify event in my plugin, from
SSAS) as far as I've seen...
I guess if I implement the server pinging feature, and do a
disconnect, i should get a E_DISCONNECT that I can use, so that
might be a (very ugly) solution.
Okay so I tried that now, with the following code:
application.onAppStart = function()
setInterval(application.pingAll, 30000);
Client.prototype.onStatus = function(info)
trace("client "+this.id+ "/"+this.ip+" onStatus with
"+info.code+", "+ info.level +": " +info.details);
Client.prototype.onResult = function(info)
trace("client "+this.id+ "/"+this.ip+" onResult with
"+info);
application.pingAll = function()
trace("Pinging "+application.clients.length+" clients");
for (i = 0; i < application.clients.length; i++)
var c = application.clients[ i ];
var r = c.call("ping", c);
trace("Pinging " + c.id + "/"+c.ip+ ", result "+r);
The result of this was, when pinging a client that was alive
I got "NetConnection.Call.Failed" immediately, but that was
expected since I haven't implement the ping function in my client.
So far so good.. Then I started another connection/stream on a
laptop, and pulled the plug.. A while later it tried to ping.. No
call to onStatus nor onResult.. waited a bit, after 5 minutes still
no call to onResult??.. return value from c.call was always true,
but after around 6-7 minutes, it started to return false instead.
But no call to onResult..
To me this seems like a bug? Or do I have to enable timeouts
or something?
I do have <AutoCloseIdleClients enable="true"> (with
60s check interval and 300 max idle) in my config, but still it
seems that the client object is alive in application.clients way
longer than 5 minutes..
Seems Adobe got a few quirks to sort out?
Thanks for any help or input!