You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@royale.apache.org by ca...@apache.org on 2019/12/25 11:53:48 UTC
[royale-asjs.wiki] branch master updated: remove content and point
to the migrated one in Royale-docs
This is an automated email from the ASF dual-hosted git repository.
carlosrovira pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/royale-asjs.wiki.git
The following commit(s) were added to refs/heads/master by this push:
new 3ef7409 remove content and point to the migrated one in Royale-docs
3ef7409 is described below
commit 3ef74092c0079971c8d9a1e1145187532c93b9e1
Author: Carlos Rovira <ca...@apache.org>
AuthorDate: Wed Dec 25 12:53:42 2019 +0100
remove content and point to the migrated one in Royale-docs
---
...yale-communication-with-AMF-and-RemoteObject.md | 60 +---------------------
1 file changed, 2 insertions(+), 58 deletions(-)
diff --git a/Apache-Royale-communication-with-AMF-and-RemoteObject.md b/Apache-Royale-communication-with-AMF-and-RemoteObject.md
index 5ee3039..a4faee8 100644
--- a/Apache-Royale-communication-with-AMF-and-RemoteObject.md
+++ b/Apache-Royale-communication-with-AMF-and-RemoteObject.md
@@ -1,59 +1,3 @@
-> **Update Oct, 15th, 2018**: We have **mx:RemoteObject** working in develop branch you can check the example here: https://github.com/apache/royale-asjs/tree/develop/examples/mxroyale/RemoteObjectAMFTest, The example can be tested as well with https://github.com/apache/royale-asjs/tree/develop/examples/amf/SampleAmfWebApp, just remember that we still doesn't support Small Messages in BlazeDS (and this should not make a big difference), so remember to disable it like we explain in this d [...]
+This content is now migrated and updated to Royale Docs in this URL: https://apache.github.io/royale-docs/features/loading-external-data/remoteobject
-AMF is a great way to send data between an Apache Royale client and a backend server. The server could be written in Java, PHP, .NET, Ruby, Python and many other backend technologies.
-
-Read more about AMF here :https://en.wikipedia.org/wiki/Action_Message_Format
-
-Apache Royale supports AMF protocol and you to demonstrate it we provide two projects:
-
-* RemoteObjectAMFTest: Is the Apache Royale Client that uses RemoteObject to communicate with the backend server to send and receive data via AMF.[Direct Link to this project](https://github.com/apache/royale-asjs/tree/develop/examples/royale/RemoteObjectAMFTest)
-
-* SampleAmfWebApp: Is a Java WebApp that uses Apache Flex BlazeDS to expose some data and objects through an AMF endpoint. [Direct Link to this project](https://github.com/apache/royale-asjs/tree/develop/examples/amf/SampleAmfWebApp)
-
-To run this example localy you can follow this steps. Note: At this time some parts of the example only can be build with maven, we'll be providing at same time ANT build, but this is not priority. If you're interested in ANT build you can submit a PR)
-
-1. Build RemoteObjectAMFTest with maven using "mvn clean install". This generates the Apache Royale client.
-
-2. Build SampleAmfWebApp with maven using "mvn clean install". This generates the Java Web App with AMF support and will overlay the RemoteObjectAMFTest client compiled in the previous step
-
-3. Launch SampleAmfWebApp in the embedded Jetty web server with "java -jar target/SampleAmfWebApp-0.9.3-SNAPSHOT-exec.war". you should be in root SampleAmfWebApp folder. Notice: that SNAPSHOT number is just an example and can be different
-
-4.- In a browser launch "http://localhost:8080" and you would see the following:
-
-
-
-## Remote Object Implementations
-### RemoteObject
-
-RemoteObject is based on the original one in Flex RPC library. It's done to work with BlazeDS, LCDS or CF AMF backend implementations. It support "clientId" management required for the backend to differentiate different connected clients.
-
-An example of use:
-
-```
- <js:RemoteObject id="service"
- endPoint = "http://localhost:8080/messagebroker/websocket-amf"
- destination = "exampleService"
- result="onResult(event)" fault="onFault(event)"/>
-```
-
-Note: BlazeDS use by default special extra serialization through small messages. For now you need to turn this feature off until we fully implement it, but BlazeDS communication will work correctly. So use this for each _channel_ in your _services-config.xml_ with:
-
-```
- <channel-definition ...>
- <properties>
- <serialization>
- <enable-small-messages>false</enable-small-messages>
- </serialization>
-```
-
-### CompressedRemoteObject
-
-A new RemoteObject, called CompressedRemoteObject, that performs compression has been added to Apache Royale. RemoteObjectAMFTest client and SampleAmfWebApp application has been updated to show this new feature. This remote object compress the AMF data with the zlib algorithm to improve the transfer times even more.
-
-
-
-### SimpleRemoteObject
-
-For more simple AMF backends probably RemoteObject will be more than you need. For this reason you can use SimpleRemoteObject that doesn't care about "clientId", or other BlazeDS functionalities.
-
-Enjoy!
\ No newline at end of file
+This page will be remove soon from the wiki
\ No newline at end of file