Day Software to Discuss Java Content Repository Standards and Enterprise Web 2.0 Applications at TheServerSide Java Symposium

LAS VEGAS, Mar 25, 2008 (BUSINESS WIRE) - Day Software (SWX:DAYN) (OTCQX:DYIHY), a leading provider of global content management software and content infrastructure software, will present a session at TheServerSide Java Symposium, highlighting the company's leadership with JSR 170, the Java Content Repository (JCR) standard application programming interface (API) for content access.
Learn Which Are The Best Stocks To Trade Today!
More Breaking News about DYIHY

Day Software to Present REST and AJAX Web Development Techniques at AJAXWorld

At the show, Day Software CTO David Nuescheler will lead a presentation, "Kickstarting JCR: TheServerSide.com as a Content Application," which will illustrate how developers can turn an existing TSS Web site into a content repository-based application. This presentation will begin with a brief introduction to the JCR and show how one can leverage the rapid prototyping aspects and flexibility of Web 2.0 within the secure, reliable environment provided by a standardized content repository. By transforming a TSS Web site, Nuescheler will combine the strengths offered by a highly interactive Web 2.0 application, enabling quick and efficient development with the benefits of content repository features, including versioning and full-text search indexing.
"By leveraging the technology strengths in both Java Content Repository and Web 2.0 applications, developers can quickly and efficiently manage content on the Web," said Nuescheler. "Our presentation will not only illustrate the development of a TSS Web site into a content repository-based application, but will also show how every application is a 'content application', and how attendees can accelerate their development cycles by leveraging the facilities that a content repository possesses."

Real-Time Java for the Enterprise

When people hear about real-time computing they often make the mistake of thinking that these have to be fast systems and are nearly always used for control of mechanical systems. It is true that in most cases the response times required are fast, but speed is not what defines a real-time system. The true core of a real-time environment is that the system will guarantee to perform some task within a pre-defined time so that the system's behaviour becomes fully deterministic.

For enterprise class applications what are the advantages (and possibly disadvantages) of deployment on a real-time system? In many cases there is no great advantage. Once the non-functional requirements of a system (load capacity, average response time, peak-load response time, and so on) have been met the application can be deployed and the customer is satisfied. Should something happen that makes a request to, say, an HR application take rather longer than usual the user simply has to wait longer; there is no measurable impact. However, for many financial, enterprise class applications failing to do something within a given time can easily be equated to a cost, possibly a very large one. Financial markets, by their very definition, are extremely volatile and computer trading systems mean that prices can change at the rate of many times a second. If one part of a system decides to make a trade based on the current price and the actual trade gets delayed for whatever reason even a small change can result in a significant loss of money. If this delay happens frequently the system soon becomes less of an advantage and more of a liability.