Archive for November 12th, 2008
Blaze and LC DS to support REST
We will soon be annoucing details of Blaze DS and LC DS to support REST in addition to AMF!!!
Why is this important?
- You can now migrate your application in stages – no need for a big bang approach
- You can create applications that can have Ajax/HTML and Flex UI to coexist
- The same business logic gets used from Flex and HTML/Ajax
Watch out for more information on this. Meanwhile, I would like to hear what you folks think about this.
Why Blaze DS?
2 reasons
Reason 1: Remoting = Faster performance
Flex enables applications to communicate with the server over AMF, a faster binary alternative to String encoding. If your business logic is available in Java, Blaze DS offers Remoting that enables Flex applications to direct communicate with your business logic over AMF.
Note: The fundamental difference between flex applications and web application is that you don’t generate your presentation logic on the server. The communication between the Flex client and your server (Blaze DS) is primarily data. Hence your application performs much faster than a typical web application.
Reason 2: Messaging = Live Flex Applications
The request response nature of HTTP makes it very challenging to create web applications that are not static with out any user interaction. Remember when you watching NFL (any sport scores) on the Internet, your screen updates every 2 minutes to get the latest scores. It is annoying and inefficient. Blaze DS offers a messaging infrastructure that enable you to build server applications that can push messages to Flex Application. Flex applications using Blaze DS don’t have to blink anymore.
To top it, Blaze DS is Open source and Free to use in production
