|
 Why did you rename FlashORB to WebORB?
Primary responsibility of the FlashORB server
was to process Flash Remoting requests. With the rise of
non-Flash rich client and increased awareness of the AJAX
approach, we decided to increase the scope of supported clients
to include JavaScipt as well as Flash. To reflect that change,
the product was renamed to WebORB Presentation Server.
TOP
Does WebORB
support all the features from FlashORB?
WebORB supports the same set of features found
in its predecessor product - FlashORB.
TOP
Is
WebORB backward compatible with FlashORB?
WebORB is fully compatible with the client
applications built for FlashORB. The product provides the same
support for the on-the-wire protocol. To eliminate any changes
on the client side for an existing client application, make sure
to register WebORB with the same URL where FlashORB used to run.
Any server-side code coupled to the FlashORB
APIs, would need to change the package/namespace name. The new
package/namespace name is "weborb" for Java and "Weborb" for
.net.
TOP
What are the
new features of WebORB?
WebORB introduces several new features. The main
two are support for AJAX clients and support for ColdFusion
components. The AJAX support provides connectivity between
JavaScript clients and all the server-side types supported by
WebORB. Using WebORB AJAX clients can easily bind to and invoke
methods on any Java or .NET object, XML Web Service, EJB or
ColdFusion Component. The same features of WebORB used by Flash
applications are now available to the JavaScript clients as
well.
The ColdFusion integration relies on the BlueDragon server by
New Atlanta. The result of the integration is the ability to
consume CFCs from AJAX or Flash Remoting clients.
TOP
Where
can I download the Rich Client System?
The Rich Client System is included with the
WebORB distribution - no additional downloads is needed.
TOP
What
client environments the Rich Client System is available for?
The 2.0 Beta 1 release supports only JavaScript
environment. Future releases will provide the ActionScript
implementation.
TOP
What
browsers has the Rich Client System been tested with?
The Rich Client System has been tested with the
following browsers:
- Microsoft Internet Explorer v5.5+
- Mozilla 1.7+
- Mozilla Firefox 1.0+
- Camino 0.8+
TOP
What
features of the Rich Client System are available in the 2.0 Beta 1
release?
The Beta 1 release of the Rich Client System
delivers the following features:
-
Object binding API - provides a way to
bind to any service type supported by WebORB
-
Synchronous and asynchronous remote method
invocations - easy-to-use, very intuitive API to invoke
server-side object methods from the client application. The
Rich Client System provides a patent-pending technology to
present any server-side object as if it is a local JavaScript
object.
-
Data binding API - The Rich Client
System works closely with WebORB to deliver database query
results to the client application. The client receives a
special object with a query data in a well structured format.
-
Data paging API - For the data returned
by WebORB in pages, the Rich Client System provides an
easy-to-use set of functions to retrieve subsequent pages
containing query results.
TOP
What
features will be added in the future releases of the product?
Future releases of the Rich Client System will
include reusable client side widgets, extensible event
framework, interactive messaging client for peer-to-peer and
broadcast messaging. We also plan to release an AJAX debugger,
client code generator and integration with most popular IDEs.
TOP
Can
I use the Rich Client System to connect to other AJAX servers?
The Rich Client System and WebORB implement an
XML based protocol to encode method invocation data. The
protocol is Web Object Literal Format (WOLF). We plan in
releasing the protocol information so other application vendors
can introduce support for the Rich Client System. At this time,
WebORB is the only server capable of processing the Rich Client
System requests.
TOP
|
