Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. Local IPC Java App <--> C++ DLL

Local IPC Java App <--> C++ DLL

Scheduled Pinned Locked Moved C / C++ / MFC
questionc++javacomsysadmin
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    ReneDalsgaard
    wrote on last edited by
    #1

    Hi There The scenario: I got one Java application (server) and multiple C++ clients. The java server is always running and the C++ clients will need to communicate with it as they are started/Stopped. The data communicated is mainly XML. All this is running on the same computer. The demands: The communication must be platform independent, at least in the Java application (i.e. no using JNI dlls) because the Java server should run unchanged and be able to communicate with clients implemented on other architectures in the future. The technique should be easy to work with, i.e. not too low level, and not over complicated (as I suspect CORBA is) The question: What communication technique/technology should I use? The considerations: CORBA Too complicated for the simple use? Sockets/Pipes Too much work for the intended simple use? XML-RPC Current my favourite. But is it too inefficient using HTTP when the communication is local? JNI Not suited for IPC unless memory mapped files are added...correct? XYMessenger As presented here. Might be suitable but how is it compared to XML-RPC? Kind Regards Rene

    I 1 Reply Last reply
    0
    • R ReneDalsgaard

      Hi There The scenario: I got one Java application (server) and multiple C++ clients. The java server is always running and the C++ clients will need to communicate with it as they are started/Stopped. The data communicated is mainly XML. All this is running on the same computer. The demands: The communication must be platform independent, at least in the Java application (i.e. no using JNI dlls) because the Java server should run unchanged and be able to communicate with clients implemented on other architectures in the future. The technique should be easy to work with, i.e. not too low level, and not over complicated (as I suspect CORBA is) The question: What communication technique/technology should I use? The considerations: CORBA Too complicated for the simple use? Sockets/Pipes Too much work for the intended simple use? XML-RPC Current my favourite. But is it too inefficient using HTTP when the communication is local? JNI Not suited for IPC unless memory mapped files are added...correct? XYMessenger As presented here. Might be suitable but how is it compared to XML-RPC? Kind Regards Rene

      I Offline
      I Offline
      igor1960
      wrote on last edited by
      #2

      My vote: Sockets. "...Ability to type is not enough to become a Programmer. Unless you type in VB. But then again you have to type really fast..." Me

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups