FluorineFX vs. WebORB

[leandrotr]

Pessoal,

Estou querendo desenvolver algumas aplicações utilizando Adobe Flex e .NET.
Pesquisei um pouco sobre ferramentas para realizar esta integração, e pelo que pude notar, as melhores são o FluorineFX e o WebORB.

Segundo vocês, qual seria a melhor, mais recomendada?

Obrigado.

Abraços!

[Vinícius Sandim]

Bom dia Leandro,

Olha optei pelo uso do Fluorine há algum tempo, pois ná época o WebOrb ainda era pago.

Sei que o Fluorine funciona muito bem, todas as minhas apps atuais usam ele, ele é bem leve e rápido.

Não conheço muito bem o WebOrb, por isso não posso dar uma opinião formada sobre ele, comecei a estuda-lo a pouco tempo, me pareceu muito bom, cheio de recursos, geração de código essas coisas.

Pelo legado que tenho com o Fluorine, últimamente tenho optado por ele.

[Ricmears]

Caros
Ressucitando o topic, o pessoal da WebORB me envio material interessante sobre o FluorineFX vs. WebORB:

WebORB vs Flourine
This is Midnight Coders own evaluation of the differences between WebORB and Flourine. It is prudent
and incumbent for potential customers to do their own evaluation before making a decision on which
solution will best meet their needs.
Messaging
------------------------
1. Integration with MSMQ: WebORB provides bidirectional integration with MSMQ. Flex
Producer/Consumer objects can communicate with messaging destinations linked with MSMQ. Any
message sent to such a destination is delivered to the corresponding queue. Also, other queue clients
(running natively in OS) may publish messages to the queues and WebORB automatically delivers them
to Flex clients. This feature is not available in Fluorine.
2. Video Streaming: WebORB can stream real-time flash video to a very large number of Flash/Flex
clients. Video may come from a FLV file or from other video producers (like live broadcasting). This
feature is not available in Fluorine.
3. Video Recording. Video/audio streamed from a webcam can be recorded in a FLV file for later
playback. This feature is not available in Fluorine.
4. Server-initiated streaming. Consider the following-scenario: server starts playback of some video
content. Multiple users connect to the server and start playing the video stream. All users can watch the
video at exactly the same timecode regardless when they connected to the server, thus creating a
"virtual movie theater". This feature is not available in Fluorine.
Data Management
---------------------------
1. WebORB sets you free from any third party components and their respective license agreements. If
you use Data Management implemented in Fluorine, you have to download LCDS and use one of its
client-side libraries to get access to the client-side API. This may not be obvious to some users, but by
doing so, you accept LCDS license agreement and thus if you end up using the client-side library even in
Fluorine, you have to pay license fees to Adobe. How do we know this? Initially we went the same route
and implemented Data Management in a similar way. Soon enough we got some alarming emails from
Adobe saying that our users would be responsible to acquire LCDS licenses if they use *any*component
from the LCDS distribution. As a result, we ended up implementing our own Data Management system.
2. WebORB Data Management provides a code generator capable of producing a complete data
management system around user data models. The generated code provides a full CRUD system for
both client- and server-side environments. With ZERO coding, developers can access data from their
database, add, delete and modify records. This feature is not available in Fluorine.
3. Client synchronization. Suppose you have two or more Flex clients connected to your database. One
makes a change in the underlying data model. All other clients automatically receive an event from the
server via data push notifying them about the change. This is WebORB Data Management. This feature
is not available in Fluorine.
Remoting
---------------------------
1. Pre- and post- invocation handling. Suppose you need to inject some code to execute before and after
some or all invocations, WebORB provides an easy to use interface to inject that custom code into the
invocation chain. This feature is not available in Fluorine.
2. Complex types and arrays in service browser. WebORB Management Console provides a way to
invoke methods with arguments such as primitives, complex types, arrays, etc. When you invoke a
method with any of these types through WebORB management console, you get a user interface that
graphically represents such a type. With Fluorine, you get a tech box regardless of whether the type is
an array, a boolean, a complex type or a date.
3. Graphical security configuration. WebORB makes it very easy to configure security directly via the
management console. You can apply security permissions to any selected method, class or the entire
namespace. You cannot do that graphically in Fluorine.
4. Code generation. WebORB code generator uses XSLT stylesheets which are easy to modify and
customize. Additionally, WebORB offers 6 different styles for code generation (AS3, AS2, Cairngorm,
PureMVC, AJAX, FMS), while Fluorone offers only 2 (AS3 and Cairngorm).
Server Extensions
----------------------------
1. Documenation Management. WebORB supports extensions for PDF generation through WebORB PDF
Generator (add-on functionality), streamlining the process of developing and deploying PDF
functionality to end-users. Flourine does not support this.
2. Messaging SDK. Applications require extensive messaging capabilities (normal for stock trading) can
benefit from development velocity benefits afforded by WebORB Messaging SDK. Flourine does not
provide this benefit.
Non-technical
----------------------------
1. Both WebORB Community Edition and Fluorine are free products, but WebORB Enterprise Edition is
backed by a US commercial entity providing professional support and training. Fluorine is managed by a
single engineer out of Romania.
2. WebORB has a significant number of major deployments (Dow Jones Big Charts, NASDAQ, SAC Capital,
Boeing, NASA JPL, US Navy, True.com, US Air Force, Mattel, HBO, Direct TV, NRA News, National
Cinemedia, EMC, Mountain Dew, Vogue, Bacardi and many more…), there is no official record of the
same traction for Fluorine.
3. WebORB is not just an integration server, the company behind it has a
solid vision and roadmap for the future of the product to include every aspect of RIAs from development
to test to runtime and business optimization. The roadmap for Fluorine remains unclear.