RIA Web application with switchable communication strategy
-
Hi, Any suggestions on how I can build an client/server architecture which has a browser-based RIA (Rich Internet Application using flex, .NET 3.0 or other) client and a server architecture that can run either on a web server (SOAP/Web services), or as an ordinary TCPIP-based application server. The option for deployment will be given the user at install time. I understand that I need to write communication services for both options, but what is the optimal choice of technology/method? The goal is to give the option to install the application on a standalone PC without IIS or any other web server installed, but still let the user interface be browser based. Jay
-
Hi, Any suggestions on how I can build an client/server architecture which has a browser-based RIA (Rich Internet Application using flex, .NET 3.0 or other) client and a server architecture that can run either on a web server (SOAP/Web services), or as an ordinary TCPIP-based application server. The option for deployment will be given the user at install time. I understand that I need to write communication services for both options, but what is the optimal choice of technology/method? The goal is to give the option to install the application on a standalone PC without IIS or any other web server installed, but still let the user interface be browser based. Jay
http://en.wikipedia.org/wiki/Rich_Internet_application[^] The current status of RIA development and adoption RIAs are still in the early stages of development and user adoption. There are a number of restrictions and requirements that remain:
led mike
-
http://en.wikipedia.org/wiki/Rich_Internet_application[^] The current status of RIA development and adoption RIAs are still in the early stages of development and user adoption. There are a number of restrictions and requirements that remain:
led mike
Thanks. However, don't focus on the RIA part of my question. That is only to show that I want a "modern" browser-based UI experience. It is the dual-protocol communication strategy which is the interesting part to me. I want to have a web/internet application (default) to be able to run on a standalone computer environment which hasn't got a webserver installed. Jay
-
Thanks. However, don't focus on the RIA part of my question. That is only to show that I want a "modern" browser-based UI experience. It is the dual-protocol communication strategy which is the interesting part to me. I want to have a web/internet application (default) to be able to run on a standalone computer environment which hasn't got a webserver installed. Jay
We are having some communictions problems. You want an internet application without the internet? :confused: If you want to use a Web Browser interface for your UI in a desktop application you can use the WebBrowser control. At this point I have no idea what you are trying to accomplish.
led mike
-
Hi, Any suggestions on how I can build an client/server architecture which has a browser-based RIA (Rich Internet Application using flex, .NET 3.0 or other) client and a server architecture that can run either on a web server (SOAP/Web services), or as an ordinary TCPIP-based application server. The option for deployment will be given the user at install time. I understand that I need to write communication services for both options, but what is the optimal choice of technology/method? The goal is to give the option to install the application on a standalone PC without IIS or any other web server installed, but still let the user interface be browser based. Jay
Jay You need to be a little more clear on what you mean by web server and ordinary based TCPIP-based application server. By web server I am assuming you literally mean a web server as in Apache or IIS. And TCPIP-based application serevr, I assume you mean Tomcat, Websphere, etc. Right? I am currently creating an RIA using flex with a .NET backend. dan
-
Jay You need to be a little more clear on what you mean by web server and ordinary based TCPIP-based application server. By web server I am assuming you literally mean a web server as in Apache or IIS. And TCPIP-based application serevr, I assume you mean Tomcat, Websphere, etc. Right? I am currently creating an RIA using flex with a .NET backend. dan
Hi Dan, Yes, you are right with the first one: I mean web server as in Apache, IIS etc. The second one I simply mean a server application that can render the RIA client without running on a web server. I will try to explain be telling you about the scenarios I see: Scenario 1 (main): The user downloads the application and deploys it on a webserver, so that the application is available for all users on the intranet (through the RIA client) Scenario 2: The user which will be one that decides that the application should be downloaded and tested on the company's own data before purchase, should be able to deploy it on his own computer/laptop as a standalone application with a database connection to the company's own production/test databases. This computer/laptop will normally not have any webserver locally installed and we cannot expect that the user will be interested or have the skills/patience to install the local IIS (or other Web server) before he can test the application. Therefore the application must be able to be deployed as a "standalone" configuration without a webserver to render the client. I hope this clarified my requirements. In the meanwhile I have found a class in .NET 2.0 (HttpListener) which can implement a web application without a web server. I appreciate more comments and ideas. Jay