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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,ff1f0403676a2300
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.68.223.73 with SMTP id qs9mr1423424pbc.7.1344863543789;
        Mon, 13 Aug 2012 06:12:23 -0700 (PDT)
Path: 
 g9ni53777092pbo.0!nntp.google.com!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
From: Marc C <mc.provisional@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: Ada Networking (General/Design)
Date: Mon, 13 Aug 2012 06:12:23 -0700 (PDT)
Organization: http://groups.google.com
Message-ID: <df59f1e0-786c-4012-ae8b-d8f518c0a5dc@googlegroups.com>
References: <08540a65-8d88-4042-b021-52c49b2e6772@googlegroups.com>
 <fi6nymfk59lc.v49zgtg4rb7e$.dlg@40tude.net>
 <2de69490-cbc2-4f58-af8a-db5bee3fd665@googlegroups.com>
NNTP-Posting-Host: 134.223.230.200
Mime-Version: 1.0
X-Trace: posting.google.com 1344863543 21531 127.0.0.1 (13 Aug 2012 13:12:23
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Mon, 13 Aug 2012 13:12:23 +0000 (UTC)
In-Reply-To: <2de69490-cbc2-4f58-af8a-db5bee3fd665@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=134.223.230.200;
 posting-account=mjE6MAoAAADjsB3NIuKgfHO4u-Elh3cb
User-Agent: G2/1.0
X-Received-Bytes: 2099
Content-Type: text/plain; charset=ISO-8859-1
Date: 2012-08-13T06:12:23-07:00
List-Id: <comp.lang.ada>

On Monday, August 13, 2012 7:33:28 AM UTC-5, Patrick wrote:

> Does anyone have a favourite approach to TCP/IP ?

After years of working with TCP/IP sockets, my favorite approach now is...not to. Not directly anyway.

There are higher-level messaging protocols that handle most, if not all, of the socket management details for you.

Among them are ZeroMQ (http://www.zeromq.org), along with its Ada binding (http://www.zeromq.org/bindings:ada), and YAMI4 (http://www.inspirel.com/yami4).

I collected ZeroMQ, AMQP, and STOMP together into a set of text-oriented messaging interfaces called TOMI_4_Ada (http://sourceforge.net/projects/tomi4ada/). 

While you still have to be cognizant of things like host names and port numbers, by and large that's about the extent of what you need to be aware of when using these high-level protocols.

If I never have to write another setsockopt(), c_select(), and accept() again, I'll be very happy :-)

Marc A. Criley