[REBOL] Re: Event driven TCP / Rugby
From: petr:krenzelok:trz:cz at: 30-Jan-2002 6:12
Brett Handley wrote:
> Hi Maarten,
>
> > Rugby does a thing Romano described in his mail, but over one connection
> > (slightly more efficient).
> > I will remove TCP transport (speed is now the same as http), and add a
>
> Why remove the "pure" solution - where it all began?
> http and tcp transports cannot share the same logic?
exactly :-) As Rebol grows, it will replace nowadays obscure "technologies"
:-) ... just kidding :-)
> > Will work in server and view scripts
> > only, as you need an event loop. And of course /deliver-on-error
> > :error-handler
>
> I don't quite understand why an event loop could not exist in a non-view
> client script if the developer added one.
> Or is that possibility still open?
>
REBOL/Core 2.5.0.3.1
Copyright 1997-2001 REBOL Technologies
REBOL is a Trademark of REBOL Technologies
All rights reserved.
Component: "Internet Protocols" (22-Mar-2001/17:38:17)
Finger protocol loaded
Whois protocol loaded
Daytime protocol loaded
SMTP protocol loaded
POP protocol loaded
IMAP protocol loaded
HTTP protocol loaded
FTP protocol loaded
NNTP protocol loaded
Script: "REBOL Extended Definitions" (24-Jan-2000/2:53:35)
Script: "User Preferences" (5-May-1999/7:34:03+1:00)
->> read clipboard://
** Access Error: Invalid port spec: clipboard://
** Near: read clipboard://
->> help event
Found these words:
event! (datatype)
event? (action)
to-event (function)
->> evt-port: open [scheme: 'event]
** Access Error: Invalid port spec: scheme event
** Near: evt-port: open [scheme: 'event]
The same kind of output will come from /Command console. As you can see, even
clipboard:// is blocked for both Core and Command. I think that RT could
rethink the issue and definitely move event system into core language, not
just View module. GUI events are just one of possible area of usage. I think
e.g. timers (just another example of event) belong definitely to Core ...
-pekr-
