Replying to myself to avoid losing someone else time and to help others in future !
requestTimeout is no longer necessary in the Royale/JS world ! One should avoid longer communications but for very, very specific cases, may be necessary a communication longer than the usual. With RemoteObject/Flex, I saw a short timeout and with requestTimeout I can enlarge this timeout (it's not exactly and I always felt a little unstable for that reason but it's working). Testing Royale SimpleRemoteObject for a test backend method that only returns after 5 minutes (an irrealist insane amount of time), the Royale frontend gets the reply exactly after that 5 minutes, so, no need anymore for requestTimeout property, for sure. The other 3 things that I mentioned before are still missing properties and a return type. It's still a requirement for me that I will investigate further because without that or a workaround, it's a blocker right now, so I can't advance without it. Hugo Ferreira <[email protected]> escreveu no dia quinta, 2/07/2020 à(s) 22:51: > I'm trying to port my main class that use RemoteObject from Flex to Royale > (SimpleRemoteObject), but it's missing a few option from the Royale > implementation: > - requestTimeout > - convertResultHandler > - convertParametersHandler > - send result (AsyncToken) >
