Applying data for a flexible .net backend application

I am going to switch to a large-scale application (client-flex, server-.net). The server side must transmit data to clients without their request, this data can be tables from the database or just integers that the application needs to consider.

I tried to consider WebOrb.net for this work, but the documentation is very poor and there is simply no support (I wanted to buy an enterprise license).

I am looking for a server-side solution that can transfer data from a .net application and SQL server for flexible clients using AMF, it should be very efficient with the amount of traffic and data.

The connection should not be one that is blocked by firewalls, because the application must be accessible to every client everywhere.

Any decent solution? BlazeDS? - Can it work with .net? stable? Life cycle? Can it work with .net? stable? WebORb.net? Does anyone have a different impression of this server and have more experience than I have with them?

I would like your answers.

Thanks a lot Avi

+4
source share
3 answers

You should check out http://www.fluorinefx.com/ This is open source and no worse than weborb. Both of them have mailing lists and with the installation of many examples (as well as transferring data to the client). If you work with .net, I would recommend FluorineFx as it is free. WebOrb can be used for free, but in a production environment you can connect only 5 ip. (there’s also a community edition, but I don’t know if you can use it in the production process).

They also support MSMQ!

In this example, you can see how to push data in flex. With FluorineFx, this is the same.

+1
source

This might be a completely insane approach, but I had previously implemented a spark chat application in a flex application. The spark chat id was associated with the user id in the flex application, and so I could send the spark client message, and then depending on the message update, the flex application or start the request

0
source

The easiest way I know is to just constantly listen with long timeouts (long poll). AMF.NET provides you the .NET support that you need. I think LiveCycle supports other data types, but BlazeDS can only support long polls.

-one
source

All Articles