World: r3wp

I try this

read daytime://time-a.nist.gov

It says the port gets opened but the awake function is not triggered

yes but your actors (open and/or read) must create a tcp port thru 
the host

a scheme is only a wrapper above a tcp connection

(or upd)

I know ..

So you have to do a open tcp://host somewhere in your code

Oh ... I didn't create the port ...

yes

ok, it will have to wait till my tv program finishes now

give me some minutes, i will write it

make-scheme [
	name: 'daytime
	title: "Daytime Protocol"
	awake: func [event /local port] [
		print ["=== Client event:" event/type]
		port: event/port
		switch event/type [
			lookup [
				print "DNS lookup"
				open port
			]
			connect [
				print "connected" 
				read port
			]
			read [
				close port
				return true ; quits the awake
			]
		]
		false
	]
	actor: [
		;open: func [port [port!]][port]
		read: func [
			port [port!] /local con
		][
			con: open rejoin [tcp:// port/spec/host ":13"]
			con/awake: :awake
			wait con
			to-string con/data
		]
	]
]

probe read daytime://time-a.nist.gov

=== Client event: lookup
DNS lookup
=== Client event: connect
connected
=== Client event: read
{
55203 10-01-07 07:51:23 00 0 0 282.6 UTC(NIST) *
}

thanks

you may add a timeout inside the wait.

can add it to the spec

I've updated my effort again ... http://rebol.wik.is/Rebol3/Schemes/Daytime

the data is returned deep inside the port object

weird !

The open function must not return the tcp port, but the fake daytime 
port.

Because if someone try to thing like this. 
>> port: open daytime://...
then 

>> read port ; ==> the wrong actor is called (not the daytime one).

it may work currently, because you didn"t add other behavior in the 
read actor, but it's just fluke

brian: there is no link to wetan, it is in the r3-alpha file share.

(graham's link above is not complete. there are a few pieces missing, 
and they are missing because the code, even tough it works, is crap 
:)

documentation in the code itself using comments

 - that only works in very simple cases. I did the network detective 
 like that...

Maxim: sorry, I don't understand your point. the code is not available 
to us, so only Carl can write the basic docs...

Steve ...good point.

Steeve ...

they can do ..

port: open daytime://
wait port 

:)

I've logged onto r3 chat a few times .. seems dead to me.

dead? it works, but noone is posting, no?

or you mean dead by activity?

dead as in dead quiet

it is dead because all R3 dev. activity is stalled ....

It is also quite hard to cut and paste as the console doesn't support 
it ..except as a dos console

Have to use the clipboard to transfer stuff to and from the r3 alpha 
console

yes, console under Windows is really bad ... also no multiline support 
for REBOL code ...

Is it better under linux?

don't know ...

Not much.

If you want to suggest a plan for better console, please do.

It would not require much on the reblib side to support a console 
-- most of the code is on the host side.

R2 console code is not reusable?

The necessary reblib calls would be for things like word completion, 
since the symbol table is internal to the lib.

ditto

R2 could be used... but, I had "imagined" there were better packages 
that we could use and get a full featured console.

well I don't use word completion ... didn't even know it existed 
for files

Le's be practical and reuse R2

Is that the most practical?  What ever happened to operating systems 
that provide a real console lib?

the most practical is to make it usable for users and optimize later 
on

Certainly, we can use our 1998ish console code to start. But, seems 
a bit backward.

lacking cut and paste as now is somewhat even more backward!

Feels like the original console of 1998 which also lacked cut and 
paste if  I recall correctly