Guest_imported
New member
- Jan 1, 1970
- 0
Hi,
I am interested in developing a large Java application that uses Flash as the "output window".
My idea is to make up some XML standards for communicating with the Flash player and then having the option to re-implement these XML standards with another player ten years down the track if Flash is not the leader, or changing the minimal amount of code as the Flash player is upgraded.
I think the Java-XML-Flash approach makes sense because:
1. Writing the whole think in Flash's JScript would mean that I'd be spending most of the time debugging when the application becomes very large. Developing with a strict language like Java is more suitable for such large projects.
2. Using pure Java means that the code is portable, and for a very long project life, that means all the difference in the world. I would like to plan the project to have a 10-year+ life, so I want the bulk of the code (business logic) to be in a portable language, what I call 'Golden Code'.
I'm really new to Flash and don't know if it is going to handle this sort of model. I am farmiliar with Java Servlets, but I have only used Java Servlets in the context of receiving an request (such as a submitted HTML form) and sending a response (such as an HTML page or sending an XML page to a XSL-HTML parser).
I'm not sure if Java Servlets are going to do the job for the Flash model I'm talking about, because we need continuous talking between the Flash player and methods within pure Java.
I think this is new ground, so it is difficult to research, but I'd love to hear any ideas.
Regards
Manlobbi
I am interested in developing a large Java application that uses Flash as the "output window".
My idea is to make up some XML standards for communicating with the Flash player and then having the option to re-implement these XML standards with another player ten years down the track if Flash is not the leader, or changing the minimal amount of code as the Flash player is upgraded.
I think the Java-XML-Flash approach makes sense because:
1. Writing the whole think in Flash's JScript would mean that I'd be spending most of the time debugging when the application becomes very large. Developing with a strict language like Java is more suitable for such large projects.
2. Using pure Java means that the code is portable, and for a very long project life, that means all the difference in the world. I would like to plan the project to have a 10-year+ life, so I want the bulk of the code (business logic) to be in a portable language, what I call 'Golden Code'.
I'm really new to Flash and don't know if it is going to handle this sort of model. I am farmiliar with Java Servlets, but I have only used Java Servlets in the context of receiving an request (such as a submitted HTML form) and sending a response (such as an HTML page or sending an XML page to a XSL-HTML parser).
I'm not sure if Java Servlets are going to do the job for the Flash model I'm talking about, because we need continuous talking between the Flash player and methods within pure Java.
I think this is new ground, so it is difficult to research, but I'd love to hear any ideas.
Regards
Manlobbi
"Smile. It makes people wonder!”