Experienced ranchers please share your wisdom. Which would be the best solution, CORBA or SOAP (or another sexy beast), based on your experience. Problem: - A Tomcat based remote web application is running on a shared web hosting site at the ISP, on machine REMOTE_BOX. - The company's customer database (Intuit Quickbooks) is running on a closely held machine in the VP Marketing's office LOCAL_BOX. - On the web server (REMOTE_BOX) we need to access "customer info" from the company's customer database (on LOCAL_BOX). Quickbooks does not provide a web access, BUT it allows us to write a thin client running locally on LOCAL_BOX. - VP Marketing would not allow us to run a web service on the LOCAL_BOX. So we decide to write a thin client on the LOCAL_BOX which would tickle the REMOTE_BOX every 30 seconds(configurable) and push data up, if needed. Remember we CANNOT guarantee that the thin client on LOCAL_BOX will be running Java code (i.e. ruling out RMI). If you notice a Design Pattern, please go ahead share it as well. Regards, dj.
Please don't post the same message in more than one forum. You obviously read more than one forum; so do the people who might answer your post. This thread is now closed. All replies to the one in the Web Services/SOAP forum.