Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status No Plans to Implement
Workspace Traveler
Created by Guest
Created on Aug 15, 2018

Recode traveler using Notes C API instead of JAVA

Traveler is mainly coded using JAVA... not a good choice for a serious 24*7 massive server side product. All other tasks are coded using the native C API, why is traveler coded in java?

  • Attach files
  • Guest
    Reply
    |
    Sep 6, 2018

    Thomas, there are several reasons:
    Performance: It is known that C++ is generally faster than Java
    Memory consumption: Linked to performance, a C application consumes by far less memory than Java
    Internal architecture: All native Domino server tasks are coded using Notes C API that is the first-level API (native) while java is just a wrapper. Why is this particular server task coded in Java while other native server tasks use the native API?

    From my point of view, the only advantage of Java (in this case) is that applications can be coded faster than with C++.

    This particular application (Traveler) is really heavy... it often requires a dedicated server. It's not a light server task. 

    Why aren't operating system built upon java? 

    Java is really useful for tons of applications... but for native system development it's not.

  • Admin
    Thomas Hampel
    Reply
    |
    Sep 6, 2018

    Another question to the author of this idea : Is there any problem with using Java? 

  • Guest
    Reply
    |
    Aug 29, 2018

    History lesson: Traveler started out as a J2EE app, able to run on Tomcat and WebSphere (It wasn't called Traveler then).  Java is the standard for these containers.  It was later ported to run directly on Domino's jvm (split between a servlet portion running in HTTP and the rest as a server task).