Re: new Eu version, no built-in socks yet

new topic     » goto parent     » topic index » view thread      » older message » newer message

----- Original Message -----
From: Everett Williams <rett at GVTC.COM>
To: <EUPHORIA at LISTSERV.MUOHIO.EDU>; <KSMiTH at PELL.NET>
Cc: Everett Williams <rett at GVTC.COM>
Sent: Thursday, November 25, 1999 9:27 PM
Subject: Re: new Eu version, no built-in socks yet


> Kat  wrote:
>
> >> Since both the Windows and 'nix platforms already support sockets
through
> >> the standard API's, what would be gained by creating built-ins to do
this
> >> in the interpreter?
> >
> >Speed and common interface.
> >
> >Kat
>
> Somebody on this list...can't remember just who at this juncture... is
always
> howling on about paradigms (might even have been me). As a paradigm, the
> Internet isn't likely to go away soon and Internet functionality through
such
> things as socks support sure makes the job a lot easier. I wouldn't mind a
> call interface to a paradigm that makes this discussion possible, but I
would
> want the calls to be the same on all platforms. That might mean that
> somebody comes up with a little lib like VEL or some free package that
runs
> on all the platforms that Eu does that would allow all versions of Eu to
make
> the same calls. Socks or some hook to IPv6 is the only form of IO that is
absolutely going to be found on every machine in the galaxy. Local IO is not
> particularly portable and therefore would not be a good candidate for
> embedding in a portable Eu, but this one sure looks like an opportunity
> for everything from multi-player games to mail programs...to whatever
> internet functionality that one can dream of. What fun. If I were going
> to embed any IO, this would be it.

Eu's lack of this caused a couple people to move from Eu to Rebol. The thing
is, i really need Eu for working code, and only a small part of Rebol's
abilities for ease of connections. Like i've said here before, rather than
making a lot of difficult calls to a big include file to do port i/o, a few
extensions to the existing file commands will do fine. Then an include file
can be made for the different protocols, and interfacing the ports to VEL,
etc. for a graphic html web browser or whatever.

Kat

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu