Re: Ada and Internet stuff

["Marin David Condic" <dont.bother.mcondic.auntie.spam@[acm.org>]

The scenario you describe is kind of where I was going with communications
links. Probably the most popular link today would be TCP/IP - although I
hesitate to make the claim because someone will come out of the woodwork
challenging that. Certainly, its *one* of the most popular. Throw on top of
that Sockets and you have a very common way of building distributed apps.
Streams would be a natural way to connect to Sockets and you'd quite often
be building a Socket system with the same compiler on the same or similar
machines. So even though streams aren't highly portable (at least in terms
of using 'Input and 'Output - but that is by far not the only means of
getting data into a stream) in all communications apps, you could still see
that a lot of communications could be 8-bit byte oriented and streams would
want to hook up to that.

MDC
--
Marin David Condic
Senior Software Engineer
Pace Micro Technology Americas    www.pacemicro.com
Enabling the digital revolution
e-Mail:    marin.condic@pacemicro.com
Web:      http://www.mcondic.com/


"Ted Dennison" <dennison@telepath.com> wrote in message
news:v9Qj7.886$F4.5311@www.newsranger.com...
>
> Well, I'd actually throw out the "data along communication links" one.
Data put
> in streams is just *not* portable, unless extreme efforts are put forth to
make
> it so (eg: GLADE).
>
> Without a lot of effort, streams are really only useful for dealing with
data
> that is going to be read and written from Ada code on the same type of
platform
> compiled with the same compiler.
>