Amn
09-12-2005, 03:00 PM
This is a server-side script issue, not a Flash player Remoting issue. Although the "NetServices.as" is available for Server MX, and has the same API, i found an issue, which I am not sure is local to my script, my server, or is a well-known bug.
The bug has to do with the following. From Server MX I call some remote .NET functions using the Remoting. I connect the gateway, everything works fine, I call some remote method, it returns fine results, and then... next time I call the same method, i wait infinitely for the results... The solution was to issue a 'connect' call again, reconnecting the gateway, with EACH remote function call. However, no documentation says I should do that, and as far as I understand you only connect to the gateway once, and as I trace my gateway connection object, it is still valid each time prior to issuing a 'call' method, without reconnecting. Flash player clients do not suffer from this issue...
Has anyone experienced this issue ?
The bug has to do with the following. From Server MX I call some remote .NET functions using the Remoting. I connect the gateway, everything works fine, I call some remote method, it returns fine results, and then... next time I call the same method, i wait infinitely for the results... The solution was to issue a 'connect' call again, reconnecting the gateway, with EACH remote function call. However, no documentation says I should do that, and as far as I understand you only connect to the gateway once, and as I trace my gateway connection object, it is still valid each time prior to issuing a 'call' method, without reconnecting. Flash player clients do not suffer from this issue...
Has anyone experienced this issue ?