Date   : Mon, 13 Jul 2009 14:48:29 +0100
From   : theom+news@... (Theo Markettos)
Subject: Master ethernet upgrade

In article <2f806cd70907110221h1e340b8qd71b79e09617509@...>
you wrote:
> F=OPENOUT("-wan-::http.sprow.co.uk:80") ?
> 
> I think that relying on port number to define protocol is asking for
> trouble .. many http and ftp services run on alternate ports, for
> various reasons..   whilst you can usualy assume that port 80 will
> have an http server on it,it's not definite... e.g.
> proxy.news.eu.easynews.com listens on a wide variety of common ports
> and they are all nntp: !

Err... are you expecting the code to know anything about the semantics of
HTTP or NNTP?  By the sounds of the above such a sockets interface would
just be raw TCP.  It's up to the application to send GET or HELO or whatever
the application protocol wants: Sprow's module just takes this stream
and sends it as TCP.

For plain TCP hostname and port is sufficient.  The application (web
browser, email client, whatever) then does the HTTP, SMTP, whatever.

Well done Sprow, very nice!

Theo