From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=0.7 required=5.0 tests=BAYES_00,INVALID_MSGID, PDS_OTHER_BAD_TLD autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,b9c9ba98cff47596 X-Google-Attributes: gid103376,public From: Bruce or Tracy Subject: Re: Message passing code Date: 1999/06/25 Message-ID: <3773F5EE.EB37831C@hiwaay.net>#1/1 X-Deja-AN: 493924540 Content-Transfer-Encoding: 7bit References: <7ksh2u$e1e2@svlss.lmms.lmco.com> <7ktlts$a7g$1@nnrp1.deja.com> <3772AD75.F5E8AAED@hiwaay.net> <7l0gj5$b62$1@nnrp1.deja.com> X-Accept-Language: en,sv,no Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Newsgroups: comp.lang.ada Date: 1999-06-25T00:00:00+00:00 List-Id: Right, Ada.Streams is not the standard - the standard was the IEEE DIS interface. Ada.Streams, now that we are using Ada95 (finally!), is the agreed upon communication interface mechanism between us and our RTI. How RTI communications with the rest of the world is decided, as I understand it, between RTI and the rest of the world. Ada.Streams is not a stardard by any means. I don't think I said that, but it maybe could have been implied. In fact, the RTI itself is in C++. They have to do a conversion from our RTI/Ada95 interface mechanism to whatever their C++ requires - I think it uses a base-type of string. Ada.Streams, as I understand the politics of the situation, is a hand-shake agreement under the table. However, our agreement was to follow their lead in using Ada.Streams. The more I use streams, the more I like them. The 'WRITE and 'READ attributes are very nice - keeps one from having to count bytes. Being Ada95 controlled, insertion and extraction errors are *almost* eliminated. Bruce Jim Rogers wrote: > > In article <3772AD75.F5E8AAED@hiwaay.net>, > Bruce or Tracy wrote: > > At work, we are currently using Ada.Stream. This is > > the mechanism for (at least parts of) HLA (High > > Level Architecture) where separate simulations > > communicate via a Run Time Infrastructure package. > > > > In the past, others used IEEE standards' formatted > > text strings in the DIS world. > > > > In these instances, the format of the message as > > well as the mechanism were a standard for that > > particular certification. > > > > Ada.Streams is a very good tool. It is not, however, a standard > beyond the world of Ada. Ada.Streams is a tool for converting > between a binary data stream and internal Ada object representation. > The binary data stream format must still be "standardized", or > at least agreed upon by all applications cooperating in a > communication community. > > -- > Jim Rogers > Colorado Springs, Colorado USA > > Sent via Deja.com http://www.deja.com/ > Share what you know. Learn what you don't.