This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I want to use bridge in between server and client to talk each others
Note that JNI only works when both sides run Java. Solutions range in complexity: 1. simple socket - client opens a socket, sends byte of data, server interprets byte, does computation, sends back byte which the client interprets. 2. "Web Service" style - client opens http connection, sends XML in SOAP format, server parses XML, does computation, sends XML reply. 3. Message style - server would have to have message capability Bill
Important: Server and client is always on the same machine.
is the opposite of this -
App A (Server) and App B (client)
When A sits on computer 1 and B sits on computer b then it uses the socket
Your problem is more related to having to communicate between 2 different "languages/technologies" on the same machine rather than having to communicate between 2 different machines.
But it looks like you are finding some solutions in that area, such as IBM's bridge2Java solution - another option I've used in this area is Jawin. [ December 01, 2005: Message edited by: Nathan Pruett ]
Joined: Jul 02, 2003
Originally posted by Nathan Pruett:
But it looks like you are finding some solutions in that area, such as IBM's bridge2Java solution - another option I've used in this area is Jawin.