Roy Gaber wrote:
> TCP
I'm not talking about the networking protocol. I'm talking about the
data protocol used at the application level - the RCP Broker message
structure itself.
The VA docs make it clear that RPC Broker communication details were
meant to be hidden to all software clients that are not a) another VistA
server, or b) Delphi clients or c) internal VistA and/or operating
system processes.
Again, It's a smart move on the VA's part because it gives the
development team quality control on client communications. And in all
fairness the the need for non-VA people to write other types of clients
may not have been a high enough priority so far.
In any case the exact details of RPC Broker messages are a mystery to
those outside the RPC Broker development team.
See the "RPC Broker Systems Manual," v-1.1, page 2-17:
"RPC BROKER MESSAGE STRUCTURE" - partly reads as follows:
The basic RPC Broker merssage structure consists of the following:
* A header portion (which includes the name of the remote procedure call).
* The body of the message (which includes descriptors, length
computations, and M parameter data).
Also, look in the "RPC Broker Technical Manual," Version 1.1; Patch
XWB*1.1*40 (Page 13-2):
"INTERFACES"
No *non*-VA products are embedded in or required by the RPC Broker
software, other than those provided by the underlying operating systems.
(emphasis theirs)
Richard Schilling
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Richard
Schilling
Sent: Friday, October 21, 2005 4:51 PM
To: hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members] new Java client for VistA.
Nancy Anthracite wrote:
You mentioned the Broker documentation, and I know you are not referring
to
this particular documentation, but I was poking around the Broker
components
while attempting to use Delphi a few months back and the Help files with
them
were really wonderful. It was like a friend was right there trying to
help
me out and was doing a bang up job of it.
From the end user standpoint and delphi developer standpoint it's
great. No question. But I haven't seen any documentation yet on the
actual protocol used on the wire yet. Have you run across this?
Richard Schilling
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
