java - Pros and cons of using BlazeDS or web services as the remoting and messaging technology between Flex view layer and Spring business layer? -


In my company, we are going to use Flex 3 for the presentation layer of a new financial web application, and the business layer There is still debate about Spring but the best message / remoting technology is going on. Can you share your own experiences with the use of one or the other technique in terms of professionals and ideas?

Use my experience, BlazeDS unless you need to use web services,

Professionals: less server-intensive, less customer parsing time, small data package (this is binary), which means that you can use different types of techniques. This is a quick call overall. Members can subscribe along with published / subscription.

Cons: Non-Flex is not compatible with the end of the front (although it is open source, so in principle, it can be.)

Webservices

Installed, very easy to read and translate cross-platform issues. Cons: More literally, if you use internal translate of XML objects of XML, then the client has to do some intense parsing. If you use objects as XML, then encapsulation will be weak (out of the call, the object will have to know the detailed information about XML objects, which means refactoring can be problematic.)

With real numbers for good comparison on actual database, see


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -