flex - Sharing Logic Between the Browser and the Server -
I am working on an app that will be like most of the app, it will load a full boat of business logic , Almost all of those who need to be executed on both the server and the Flash-based client ... and I am trying to figure out the best (least complex) way to implement the Rule Engine.
Here are the parameters of the problem:
- The Rule Engine should run on a web browser (i.e., in the Flash Player) and on the server. Duplication of logic (for example, by typing "server" version and a "client" version) would be an unacceptable risk.
- Input / output data is quite complex, hence the serialization is a non-problematic problem. We are currently using AMF for the needs of all our serialization, and using another protocol will add important complexity. .. then it should probably be avoided.
- This is unable to implement the "rule description language". Experiments have shown that the rules are complicated enough that any such language will need to be completed Turing ... whatever significant quantity Will add complexity to
- The rules do not require the engine to make something, but not too much service calls.
Currently, the best claimants are:
-
Writing code in the action script, then running it on the server starts the example of AVM in theory It is possible to carry a gateway for a long time, then pass the data back and forth in such a way ... but it seems less than ideal. Is there a "good" way to do this?
-
Writing the code in Hock I do not know anything about HEXE AMF support, so it could be a deal breaker.
-
Something related to Tamarine seems a viable option, but I have not done enough research to tell in any way.
So, what do you think? Is any of these options better than other people?
Finally, thanks for reading this wall of text :)
How many data are you talking about? If you want to run it on the server and use the queue or something then you can use the wind.
Comments
Post a Comment