I wonder if it's even practical to continue to use the existing
portability guidelines without some update. For example the limit on
string length forces modules using TCP/IP to incur a lot of overhead
and run much more slowly than they would otherwise. More generally, if
OpenVistA is to interopera
Dear Chuck,
You are correct, of course. The OpenVistA programming standards have to
include the portability standard.
Yours truly,
Rick
On Wed, 2005-04-27 at 18:32, chuck5566 wrote:
> Maybe I just missed it, but I would hope that there would also
> be consideration for the VA's, and possibly ev
VA's FOIA. That would be the
> Class II code. Is that true?
>
> Jim Gray
>
> - Original Message -
> From: "Frederick D. S. Marshall" <[EMAIL PROTECTED]>
> To: "Hardhats"
> Sent: Wednesday, April 27, 2005 5:06 PM
> Subje
ssage -
From: "Frederick D. S. Marshall" <[EMAIL PROTECTED]>
To: "Hardhats"
Sent: Wednesday, April 27, 2005 5:06 PM
Subject: [Hardhats-members] Seattle OpenVistA R&D Meeting
Dear Hardhats,
Thursday, May 12th to Sunday, May 15th, WorldVistA is holding a small
techni
Maybe I just missed it, but I would hope that there would also
be consideration for the VA's, and possibly even the MDC's,
portability standards. Otherwise very encouraging.
On Apr 27, 2005, at 6:06 PM, Frederick D. S. Marshall wrote:
Dear Hardhats,
Thursday, May 12th to Sunday, May 15th, WorldVis
Dear Hardhats,
Thursday, May 12th to Sunday, May 15th, WorldVistA is holding a small
technical meeting to verify, package, and release OpenVistA version 4.
Since this will be a technical meeting, it will not make a good venue
for those seeking an introduction to VistA, or looking for installs on
