[REBOL] system/ports/wait-list usage
From: rebol-list2::seznam::cz at: 23-Dec-2002 2:33
Hello rebol-list,
as I'm experimenting with ports now, I thoght it would be good to
use the system/ports/wait-list block as the main wait block instead
of my own block variable, but it looks, that it's not possible to
insert time into system/ports/wait-list block:
>> p: open/direct/no-wait tcp://:8080
>> wait-list: [p 0:0:1]
== [p 0:00:01]
>> wait/all wait-list
== none ;the timeouted event
>> system/ports/wait-list: [p 0:0:1]
== [p 0:00:01]
>> wait/all system/ports/wait-list
** Script Error: Invalid argument: p
** Near: wait/all system/ports/wait-list
>> system/ports/wait-list: reduce [p 0:0:1]
== [
make object! [
scheme: 'tcp
host: none
port-id: 8080
user: none
pass: none
...
>> wait/all system/ports/wait-list
** Script Error: Invalid argument: 0:00:01
** Near: wait/all system/ports/wait-list
is there any reason for that? How to use the system/ports/wait-list
with possibility to have timeouts if the system is iddle (so I can do
some tasks)
is there already some new documentation on ports?
is it better to use port's awake function (in the handler object) to
process some data or to use block with port and handler function as
it's used in the dispatch (I've never used the dispatch function anyway)
I would found it useful but it looks that it's not possible to use the
awake function on some type of port schemes (for example console)
=( Oliva David )=======================( [oliva--david--seznam--cz] )==
=( Earth/Europe/Czech_Republic/Brno )=============================
=( coords: [lat: 49.22 long: 16.67] )=============================
