Hi,
most of the time, Royale classes are not exactly as MX classes, since in
Royale we try to stick with PAYG concepts and could not have APIs that are
for "just in case" scenarios.
Being said that don't know if "request" is something is missing or is
something Alex and others want to implement in the HTTPService royale
version. But if you want 1:1 compatibility maybe is better to use the MX
version.
IMHO, I use to work with new royale UI set concepts (Jewel) but combine
with other "infrastructure" code that is in MX emulation (mostly AMF,
HTTPService, Formatters,...), so migration is more easy, but leverage the
new things we have today in browsers and interfaces.
El vie., 12 abr. 2019 a las 10:18, choirul anam (<ichsan.a...@gmail.com>)
escribió:
> How to convert mx:HTTPService to js:HTTPService ?
>
> <mx:HTTPService id="save_data" url="some/php/service.php" useProxy="false"
> method="POST"
> resultFormat="text" result="save_data_resultHandler(event)"
> showBusyCursor="true">
> <mx:request xmlns="">
> <param1>{value1}</param1>
> <param2>{value2}</param2>
> <param3>{value3}</param3>
> </mx:request>
> </mx:HTTPService>
>
> I don't see <js:request>
>
> Regards,
> Choirul
>
>
>
>
> --
> Sent from: http://apache-royale-users.20374.n8.nabble.com/
>
--
Carlos Rovira
http://about.me/carlosrovira
