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
R

ReneDalsgaard

@ReneDalsgaard
About
Posts
2
Topics
2
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Problems calling JavaScript from VC++
    R ReneDalsgaard

    Hi there I want to use some javaScript from VC++ (an XPointer implementation) and everything works fine with execScript on the IHTMLWindow2 interface. But... Then I want to receive some Xpointer data from another process. I start a VC++ thread and once it is finished and has received the data it sends the data back to my BHO. I once again use the exact same code from obove that worked before only now the execScript returns the error value -2147418113 which translates to "Catastrophic failure". Why? Is it the thread maybe, interrupting the browser when its not ready to run JavaScript. Anyone recognize or know how to solve this? Kind regards Rene.

    C / C++ / MFC c++ javascript help tutorial question

  • Local IPC Java App <--> C++ DLL
    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

    C / C++ / MFC question c++ java com sysadmin
  • Login

  • Don't have an account? Register

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