Welcome!

@CloudExpo Authors: Zakia Bouachraoui, Pat Romanski, Elizabeth White, Liz McMillan, AppDynamics Blog

Related Topics: Java IoT, Microservices Expo, IBM Cloud, Weblogic

Java IoT: Article

Breaking News: $92 Million Settlement in Kodak-Sun Java Patents Case

For the $92 million Sun receives a license from Kodak and can declare 'business as usual' in Javaland

Related Links:
  • Java Costs Sun $92 Million
  • Java Patents: "Software and Patents
  • Kodak Wins vs Sun

    The trial in the U.S. District Court for the Western District of New York in Rochester involving Eastman Kodak Co and Sun Microsystems will no longer be entering its penalty phase, as it was otherwise expected it would today. The parties agreed instead this morning to an out-of-court settlement, under which Sun has agreed to pay Kodak $92 million for a license with respect to the three US patents Java has been found to breach..

    Accordingly, Judge Michael Telesca has signed an order formally dismissing the case - "with prejudice."

    It was just last Friday that a federal jury ruled in favor of Kodak in its dispute over Java, in which it alleged that the middleware mechanisms provided by Sun Microsystems' world-beating language in fact infringe patents Kodak acquired from Wang Laboratories Inc. in 1997.

    At the time of the jury verdict, a spokesman for Kodak said: "Kodak has and continues to make substantial technology investments to ensure high-quality products. We are pleased that the court has validated Kodak's intellectual property rights protecting these valuable innovations."

    Now, despite having argued throughout the 3-week trial that Java did not infringe on the Kodak patents and that, even if it did, the patents were invalid, Sun has evidently decided that a speedy settlement is imore aligned with its - and Java's - interests than further days in court. For the $92 million Sun receives a license and can declare 'business as usual' in Javaland.

    In pre-trial documents Eastman Kodak Co lawyers had indicated that in the penalty phase the company would be asking for $1.06 billion in lump-sum royalties - a figure that represents half of Sun's operating profit from the sales of computer servers and storage equipment between January 1998 and June 2001. So $92 million is quite a bargain, many will doubtless argue.

    By dismissing the case "with prejudice," Judge Telesca is indicating that the door is closed to Eastman Kodak Co. filing suit elsewhere in this matter. To do so would risk its infringement claim being dismissed completely. In the court docket Telesca also stated that the US District Court would be making sure that the terms of the agreement were properly implemented.

    The cash settlement brings to an end a high-profile situation which has caused an outcry about the possible inadvisability of computer software being subject to US patent law, on the basis that perhaps copyright and trademarks are enough.

  • Graphic: Richard Silverberg ([email protected]) SYS-CON Media

    Sun's president and COO, Jonathan I. Schwartz, who is on record recently as saying that he believes passionately in patents, told the Associated Press this afternoon: "We are eager to put this punitive litigation behind us."

    Sun appears ultimately to share Schwartz's passion, then, and has today shown itself to be willing to invest $92 million of its substantial cash war chest in proving it.


    Related Links:

  • Java Costs Sun $92 Million, Ending "Punitive Litigation"
  • Java Patents: "Software and Patents Don't Belong Together"
  • Kodak Wins vs Sun: Java Infringes Kodak Patents
  • More Stories By Java News Desk

    JDJ News Desk monitors the world of Java to present IT professionals with updates on technology advances, business trends, new products and standards in the Java and i-technology space.

    Comments (4)

    Share your thoughts on this story.

    Add your comment
    You must be signed in to add a comment. Sign-in | Register

    In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


    CloudEXPO Stories
    GCP Marketplace is based on a multi-cloud and hybrid-first philosophy, focused on giving Google Cloud partners and enterprise customers flexibility without lock-in. It also helps customers innovate by easily adopting new technologies from ISV partners, such as commercial Kubernetes applications, and allows companies to oversee the full lifecycle of a solution, from discovery through management.
    Skeuomorphism usually means retaining existing design cues in something new that doesn’t actually need them. However, the concept of skeuomorphism can be thought of as relating more broadly to applying existing patterns to new technologies that, in fact, cry out for new approaches. In his session at DevOps Summit, Gordon Haff, Senior Cloud Strategy Marketing and Evangelism Manager at Red Hat, discussed why containers should be paired with new architectural practices such as microservices rather than mimicking legacy server virtualization workflows and architectures.
    Using serverless computing has a number of obvious benefits over traditional application infrastructure - you pay only for what you use, scale up or down immediately to match supply with demand, and avoid operating any server infrastructure at all. However, implementing maintainable and scalable applications using serverless computing services like AWS Lambda poses a number of challenges. The absence of long-lived, user-managed servers means that states cannot be maintained by the service. Longer function invocation times (referred to as cold starts) become very important to track, because they impact the response time of the service and will impose additional cost. Additionally, the transition to smaller individual components (much like breaking a monolithic application into microservices) results in a simpler deployment model, but makes the system as a whole increasingly complex.
    Using serverless computing has a number of obvious benefits over traditional application infrastructure - you pay only for what you use, scale up or down immediately to match supply with demand, and avoid operating any server infrastructure at all. However, implementing maintainable and scalable applications using serverless computing services like AWS Lambda poses a number of challenges. The absence of long-lived, user-managed servers means that states cannot be maintained by the service. Longer function invocation times (referred to as cold starts) become very important to track, because they impact the response time of the service and will impose additional cost. Additionally, the transition to smaller individual components (much like breaking a monolithic application into microservices) results in a simpler deployment model, but makes the system as a whole increasingly complex.
    With the rise of Docker, Kubernetes, and other container technologies, the growth of microservices has skyrocketed among dev teams looking to innovate on a faster release cycle. This has enabled teams to finally realize their DevOps goals to ship and iterate quickly in a continuous delivery model. Why containers are growing in popularity is no surprise — they’re extremely easy to spin up or down, but come with an unforeseen issue. However, without the right foresight, DevOps and IT teams may lose a lot of visibility into these containers resulting in operational blind spots and even more haystacks to find the presumptive performance issue needle.