[Oberon] Re. TCP/IP networking
Thomas Frey
thomas.frey at alumni.ethz.ch
Mon Dec 11 09:25:26 MET 2006
A short introduction of TCP in Aos (WinAos) can be found as a pdf file at
http://bluebottle.ethz.ch/docu/network/AosNetIntro2002.pdf
or the mirrror:
http://www.bbos.org/ethmirror/bluebottle.ethz.ch/docu/network/AosNetIntro2002.pdf
The introduction is a bit old, but changes are minor (they reflect
some simplifications and the support of IPv6). The examples cited in
the documentation are contained in the release and should be up to
date.
--Thomas
On 12/11/06, easlab at absamail.co.za <easlab at absamail.co.za> wrote:
> Eric wrote:
> > I wish to write a simple networking application. Is there an Oberon
> > compiler (for Windows or Linux) that comes with a module library
> > for TCP networking?
>
> This is not a direct answer, but a just a qwik cutNpaste-demo of how
> I would try to find out.
>
> Applying System.Directory ^ to *TCP* shows:--
> ..
> NetTCP.Obj
> BAK:AosTCP.Obj
>
> Applying Watson.ShowDef ^ to NetTCP.Obj shows:--
>
> NetTCP.Def == IMPORT SYSTEM, NetPorts, NetIP;
> PROCEDURE Send (C: ..
> PROCEDURE Receive (C: ...
> PROCEDURE Connect (VAR C: ...
> ..
> PROCEDURE Start;
> PROCEDURE Stop;
> PROCEDURE ShowState;
> -----------
> Applying Watson.ShowDef ^ to AosTCP.Obj shows:--
>
> AosTCP.Def ==
> IMPORT AosIP, NetSystem, Kernel, Modules, Files, OFS, NetBase, NetPorts,
> NetIP, NetUDP,
> NetTCP, NetDNS, Input, V24, Texts, Objects, Display, Fonts, Reals,
> Oberon, Viewers,
> TextFrames, MenuViewers, Strings, Dates, AosOut, Out;
> TYPE
> Connection = POINTER TO RECORD
> PROCEDURE Available (): LONGINT;
> PROCEDURE Close;
> PROCEDURE Open (lport, fip, fport: LONGINT; VAR res: LONGINT);
> PROCEDURE Receive (VAR data: ARRAY OF CHAR; ofs, size, min:
> LONGINT; VAR len, res: LONGINT);
> PROCEDURE Send (VAR data: ARRAY OF CHAR; ofs, len: LONGINT;
> propagate: BOOLEAN; VAR res: LONGINT);
> END;
>
> ?! this one looks like an OOD approach ?
> -----------
> So to me it seems that TCP modules/libraries for N-O & Aos, exist.
> And included in N-O [& Aos presumably] there are
> Windows & Linux & standAlone compilers for the code.
>
> AFAIK, nicely documented libraries don't exist. This, apparently
> because ETH systems are evolved from student projects;
> ie. the short term view of 'my project' is followed, rather than
> 'how to make it extendable by others'.
>
> == Chris Glur.
>
>
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon
>
More information about the Oberon
mailing list