--- Kevin Toppenberg <[EMAIL PROTECTED]> wrote: > Well, I guess smarter people than me have thought about this. But > then again, the project did get shut down. I wonder why there is a > need to change the server side? Couldn't a java app talk to existing > server software? Java doesn't necessarily have to talk to an > intermediate, I'm guessing. > > Kevin
There are a lot of issues here, not the least of which is intetgrating VistA into a larger framework. But theoretically, is an approach of the type you describe possible? Recall that the RPC Broker uses a protocol that was invented as part of VistA, it is not at all standard. You could implement, say, JMS on the server side, but not without a fair amount of work (and I don't even know if the TCP/IP support available at the MUMPS level is even up to the task). Conversely, you could implement a Broker client in Java. But there's a much (in my opinion) serious problem, and that's that there is no real abstraction here: the choice of technology (on both ends) remains "hard-wired", and that is something that really needs to be avoided. Historically, this (lack of abstraction) has been an area of weakness for VistA, and I think it's time to do something about it. === Gregory Woodhouse <[EMAIL PROTECTED]> "All truth passes through three stages: First, it is ridiculed. Second, it is violently opposed. Third, it is accepted as being self-evident." --Arthur Schopenhauer ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
