Examples of ClientFX

ClientFX handles Java and JavaFX Script applications on the desktop. ClientFX includes a bundle of Java, JavaFX, security and the browser plug-ins to enable fx:// clickable links.

The JavaFX Client

The recent announcement of JavaFX brings the world of Rich Internet Applications (RIA) to the Java world proper. JavaFX Script allows the mix of a very scaleable development environment, Java, and the declarative and rich front end development that is JavaFX Script. Highly rich and interactive user interfaces can be created in JavaFX, bringing a well needed client answer to Java developers. JavaFX compares favorably with Flash technology and MS Silverlight, but arguably a less compromising development platform behind it. ServerFX and ClientFX together make sense of this technology and provide a systems approach that allows an enterprise to deploy, manage and upgrade applications over time with the ease and accessibility that makes browser access transparent and easy for consumers or corporate employees.

Performance

ServerFX performs well for good reason. In a traditional web environment each click in the browser creates a new connection to the web server and a lot of activity for server side computing to create the next page to be viewed in the browser, consuming network bandwidth too. ServerFX in concert with ClientFX uses the power of the client. ServerFX delivers code that is running on the client, repetitive connections are not made, moreover, code is only delivered once, cached, and only updated in the areas of change.

Ease of Development and Scale

Development is easy, just ignore us ! Develop your application stand alone, as developers naturally do for client side operation. When it is functional, and perhaps using a local database just drop the code in the ServerFX repository and make the appropriate fx:// link on the web site where you need it. The application is now live, always up to date and can be made to use the server database and resources by tagging objects as server side (without code re-write).

Security

Complexity and security are not complementary. The baseline for all activity on the server is the Java Virtual Machine, which not only is a well known secure sandbox, but it removes a whole class of typical attacks and abuses that are inherent to native code. Fine grained policy control is configurable where needed, but the default is secure as such can be ignored in most cases. There are no deployment descriptors, no mappings, no handlers, externally declared resources, or other indirections. The server runs, holds server side objects and delivers and updates code as needed from on directory, the repository. Simple.